Data collection system and method for fleet management

ABSTRACT

Embodiments of the invention are directed a data communication system and method for a fleet management system configured to assist with monitoring and managing a fleet of one or more powered machines and one or more human operators.

BACKGROUND

Outdoor power equipment is widely used for performing maintenanceoperations and modifications of land areas, including landscaping,forest care, lawn mowing, etc. Examples of such equipment include stringtrimmers, brush cutters, chain saws, blowers, aerators, spreaders,sprinklers, edgers, dethatchers, riding lawn mowers, walk behind lawnmowers, robotic lawn mowers, other cutting machines, etc. Usually theequipment is operated and controlled by an operator performing variousactions in the area being worked and, in many situations, particularlyin cases of professional use, at least two operators are workingtogether in the same land area. In cases of large scale maintenance workwith a fleet comprising multiple operators, e.g., as in landscapingindustries, it may be difficult to keep track of the many operators andmachines involved in a maintenance operation. Likewise it may becomplicated to keep informed about the status of individual machinesthat are part of the fleet. This can lead to a situation where it ismore or less impossible to be updated on the general performance of amachine fleet (e.g., how the different machines have been handled, theamount of working hours, performance, efficiency, etc.) and it may alsobecome difficult to know the operational status (e.g., repairs,maintenance, cost of operation) of individual machines. This may causeadditional costs related to repairs and downtime.

Another challenge related to fleet management is the amount of turnoverof workers and the frequency with which inexperienced newcomers areplaced in charge of a machine. Often there is a start-up period duringwhich a beginner will be relatively inefficient. It may be difficult tomonitor the beginner and provide the beginner or even other workers withdetailed feedback regarding technique and machine operation simplybecause it is very inefficient to keep a constant watch duringprogressing working operation. Even after finishing an activity, it maybe hard to provide constructive advice. Therefore worker training oftentakes much longer than desired. This may lead to inefficient and unsafeuse of the machine, increased emission and fuel consumption, andincreased wear and tear on the equipment.

Large-scale maintenance work such as landscaping, foresting, and groundcare often involves a number of operators working in parallel leading toa very dynamic and continuously changing operative situation. Such asituation can easily get complex and may even involve a safety risk. Forexample, when several persons are spread out in an area it may bedifficult for the individual person to keep track of surroundingco-workers due to characteristics of the landscape, noise levels, andreduced visibility. Under these conditions, two or more operators mayaccidentally get too close and interfere with each others work. Thiscould lead to damage to the equipment and, in a worst case scenario,injury to the personnel.

SUMMARY OF SOME EMBODIMENTS OF THE INVENTION

Some embodiments of the present invention provide a fleet managementsystem which is cost efficient, intuitive and easy to implement, andwhich is suitable for a dynamic fleet comprising often a plurality ofoperators handling a plurality of powered machines, such as in the caseof professional grounds care, landscaping, forest work, etc. It is,therefore, an object of some embodiments of the invention to provide asystem that assists with collection of informative data related to therunning of individual powered machines, and to use this collected datato evaluate the performance and status of the machine. It is a furtherobject of some embodiments of the invention to provide a quick,efficient, and automated way of pairing a specific machine to a specificoperator who has been running the machine, thereby being able to matchthe performance of the machine to the behavior of a specific operatorand evaluate the operator's performance, e.g. for training purposes. Itis a further object of some embodiments of the invention to provide afleet management system for monitoring a fleet comprising a plurality ofoperators handling a plurality of powered machines, where the fleetmanagement system provides a situational awareness regardingproductivity, efficiency, health, safety, service status, quality,location, etc., of the fleet including the fleet's equipment, operators,teams, customers, jobs, etc. Another object of some embodiments of theinvention includes achieving one or more of the above objects in a morecost effective manner. Other objects of various embodiments of theinvention will become clear from the following description and drawings.

Some embodiments of the invention provide a fleet management system forassisting with management of one or more pieces of equipment and one ormore equipment operators. The fleet management system may include, forexample, an identification unit configured to be worn or carried by ahuman operator, wherein each identification unit comprises anidentification unit transmitter communicably coupled to a memory,wherein the identification unit's memory comprises stored therein anoperator identification code uniquely associated with a specificoperator, and wherein the identification unit is configured towirelessly communicate the operator identification code via theidentification unit's transmitter. The fleet management system mayfurther include an equipment data sensor associated with a specificpiece of equipment, the equipment data sensor comprising a processingdevice communicably coupled to a memory, a receiver, and at least onesensor configured to sense data about the equipment, operation of theequipment, or the equipment's environment. The processing device of theequipment data sensor may be configured to: (i) use the receiver toreceive the operator identification code transmitted by theidentification unit's transmitter; and (ii) store the operatoridentification code in the memory with the data about the equipment,operation of the equipment, or the equipment's environment.

Embodiments of the invention also provide a method of monitoringequipment and/or equipment operators. The method may involve, forexample: (i) providing each of a plurality of operators with anidentification unit to be worn or carried by the operator whenever theoperator is operating the equipment, wherein each identification unitcomprises an identification unit transmitter communicably coupled to amemory, wherein the identification unit's memory comprises storedtherein unique operator identification code that can be uniquelyassociated with one of the plurality of operators, and wherein theidentification unit is configured to wirelessly communicate the operatoridentification code via the identification unit's transmitter; (ii)providing each of a plurality of pieces of equipment with an equipmentdata sensor associated with a specific piece of equipment, the equipmentdata sensor comprising a processing device communicably coupled to amemory, a receiver, and at least one sensor configured to sense dataabout the equipment, operation of the equipment, or the equipment'senvironment; (iii) automatically receiving, via the receiver, theoperator identification code transmitted by the identification unit'stransmitter; and (iv) storing the operator identification code in thememory with the data about the equipment, operation of the equipment, orthe equipment's environment.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described some embodiments of the invention and objectsthereof in general terms, reference will now be made to the accompanyingdrawings, wherein:

FIG. 1 illustrates schematically an overview of a fleet managementsystem, according to some embodiments of the invention;

FIGS. 2A and 2B provide a block diagram showing components of a fleetmanagement system according to some embodiments of the invention;

FIG. 3A is a schematic diagram of a universal equipment data sensor,according to some embodiments of the invention;

FIG. 3B illustrates one possible construction and installation system ofan equipment data sensor according to some embodiments of the invention;

FIG. 4A is an electrical diagram of an equipment data sensor, accordingto some embodiments of the invention;

FIG. 4B is an electrical diagram of a RPM sensor used in an equipmentdata sensor, according to some embodiments of the invention;

FIG. 5 illustrates another construction and installation system of anequipment data sensor according to some embodiments of the invention;

FIG. 6A is a flow chart illustrating a process performed by the fleetmanagement system to collect and utilize data from one or more fleetsaccording to some embodiments of the invention;

FIG. 6B is a flow chart illustrating various modes of operation of anembodiment of the equipment data sensor and a process performed by theequipment data sensor for selecting the proper mode of operation andcommunicating with other devices in the fleet management system,according to some embodiments of the invention;

FIG. 7A is a schematic diagram illustrating automatic operatoridentification and operator-equipment pairing according to someembodiments of the invention;

FIG. 7B is a flow chart illustrating automatic operator identificationand operator-equipment pairing according to some embodiments of theinvention; and

FIG. 7C is a flow chart illustrating a process that may be performed byan equipment data sensor to look for, monitor, and store operatoridentification codes from a plurality of operator identification codeswithin range of the equipment data sensor, according to some embodimentsof the invention.

DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention now will be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like numbers refer to like elements throughout.

Fleet Management System

Embodiments of the invention are directed to and/or facilitate systemsfor assisting with management of a fleet of outdoor power equipmentand/or equipment operators. Therefore, embodiments of the invention aredirected to systems for collecting, communicating, processing, and/orpresenting data related to outdoor power equipment, operators of theequipment, and/or tasks performed by the equipment. Although the term“fleet” is used herein to describe the system, it will be appreciatedthat, depending on the user of the system, the “fleet” may comprise manymachines of many different types with many different operators, or, forsome users, may comprise only one or two machines with only one or twooperators. Furthermore, although embodiments of the invention describedherein have often been particularly configured for use with outdoorpower equipment, some embodiments, aspects, and/or components of theinvention may have broader applicability and may be similarly used tosense and/or manage information from and/or about other types ofmachines and/or the operators of the machines.

FIG. 1 illustrates a high-level view of a fleet management system 100according to some embodiments of the invention. The fleet managementsystem 100 generally includes: (1) a data collection and communicationsystem 110 for collecting data from the equipment and the equipmentoperators and communicating the data to a central location; and (2) adata management and presentation system 150 for receiving the collecteddata, processing the collected data into useful data and formats, andpresenting the processed data to persons or systems that can utilize thedata for management of the equipment and/or operators.

The data collection and communication system 110 is, in someembodiments, applied in connection to land maintenance and/ormodification operations, including such operations as landscaping (e.g.,lawn mowing, edging, trimming, aerating, clipping, clearing, seeding,concrete or stone cutting, etc.) and forest care (e.g., forest thinning,clearing, brush cutting, etc.). These operations may be undertaken by afleet owner 101 who owns a fleet of one or more pieces of equipment. Thefleet owner 101 may be one or more individual persons or a company. Theequipment may include, for example, a handheld trimmer 121, a ride-onlawn mower 122, a chainsaw 123, and a walk-behind lawn mower 124. Itwill be appreciated that, in some embodiments, the equipment may be anyoutdoor power equipment, or even any other type of equipment, including(without limitation) zero-turn riding mowers, articulating ridingmowers, lawn tractors, robotic lawn mowers, string trimmers, edgers,hedgers, brush cutters, chainsaws, walk-behind lawn mowers, aerators,tillers, dethatchers, seeders, spreaders, sprayers, stump grinders,stone/concrete cutters, blowers, sprinklers, and/or the like.

Except in the case of robotic equipment, the equipment is typicallyoperated by one or more operators, who may be different persons from(e.g., employees of) or the same person as the fleet operator 101. Inthe illustration, the handheld trimmer 141 is operated by one operator145, the riding lawn mower 142 is operated by another operator 146, thechainsaw 143 is operated by another operator 147, and the walk behindmower 144 is operated by yet another operator 148.

According to the embodiment shown in FIG. 1, the data collection andcommunication system 110 comprises an equipment data sensor installed ineach piece of equipment, an operator identification unit uniquelyassociated with each operator; and one or more communication units. Forexample, in FIG. 1, the handheld trimmer 141 has an equipment datasensor 121 installed therein/thereon, the riding lawn mower 142 hasanother equipment data sensor 122 installed therein/thereon, thechainsaw 143 has another equipment data sensor 123 installedtherein/thereon, and the walk behind mower 144 has yet another equipmentdata sensor 123 installed therein/thereon. The equipment data sensorsgather data about the status and operation of the equipment on which itis installed and, in some embodiments, may also gather data about theequipment's environment, including data about the equipment's operatorand other nearby persons and equipment. The equipment sensors may beinstalled in the equipment during manufacture of the equipment or, insome embodiments, may be after-market additions to the equipment. Insome embodiments the equipment data sensor is a self-powered (e.g.,battery-powered) universal sensor that can be installed on differenttypes of equipment with little or no modification to the sensor and/orthe equipment, while in other embodiments the equipment data sensor maybe specifically tailored for one or more particular types of equipmentand/or integrated into the equipment's hardware. Embodiments of theequipment data sensors will be described in more detail below.

As also illustrated in FIG. 1, each operator has an identification (ID)unit associated with an operator ID code that uniquely identifies theoperator. In this regard, the operator 145 of the trimmer 141 has an IDunit 131, the operator 146 of the riding mower 142 has another ID unit132, the operator 147 of the chainsaw 143 has another ID unit 133, andthe operator 148 of the walk behind mower 144 has yet another ID unit134. The ID unit may be, for example, a data card that the operatorholds in a clothing pocket or on a lanyard. In other embodiments, the IDunit may be a key fob, wristband, ankle band, ring, watch, dongle,and/or other wearable article. In still other embodiments, the ID unitis a data unit stored on the operator's mobile phone 116, as alsoillustrated in FIG. 1. Embodiments of the ID units will be described inmore detail below. The operator ID code may uniquely identify aparticular operator by way of being unique amongst the ID codes inexistence of at least amongst those used in a particular fleet or area,thereby allowing the ID code to uniquely identify the operator that iscarrying the ID unit in which the ID code is stored. The fleetmanagement system may or may not have a database associating each IDcode with actual operator names and, in some embodiments, may onlyuniquely identify the operator using the actual ID code or some otherparticular code that a user can then, on his or her own, link to anoperator name.

Each equipment data sensor is configured to identify any ID units withina predetermined range (e.g., within range of a radio-frequency antennain the equipment data sensor) and, in some embodiments, the equipmentdata sensor wirelessly obtains an ID-code stored in each ID unit withina particular range. In this way, the equipment data sensors can storeinformation about which operator is using or is near each piece ofequipment at different points in time. For example, the equipment datasensor 123 in the chainsaw 143 may periodically look for any ID unitswithin range of its wireless transceiver and, in doing this, identifythe ID unit 133 held by the operator 147 of the chainsaw 143. Theequipment data sensor 123 may store this information along with otherequipment and environment data that it periodically collects. Likewise,the equipment data sensor 122 in the riding lawn mower 142 alsoperiodically looks for any ID units within a certain range and may, forexample, find both the ID unit 132 held by the operator 146 of theriding mower 142 and the ID unit 131 held by the operator 145 of thetrimmer 141 who happens to be, at this time, trimming nearby to wherethe riding lawn mower 142 is being operated. In such situations, theequipment data sensor 122 may be configured to store both IDs. As isdescribed in greater detail below, the equipment data sensor 122 oranother device that receives data therefrom may be able to distinguishbetween the two IDs to determine (e.g., based in whole or in part onsignal strength) which ID represents the operator of the riding lawnmower 142 and which ID is that of another person located proximate to,but not operating, the riding lawn mower 142.

In some embodiments of the fleet management system 100, some equipmentmay not use ID units and may, instead, have a biosensor, such as afingerprint reader or an iris scanner, installed thereon for identifyingthe operator of the equipment.

In one or more of these ways, the equipment data sensor gathers dataabout the operator, nearby operators, and/or nearby equipment. Theequipment data sensor also has one or more sensors built into it and/oris communicably coupled to one or more sensors on the equipment thatmeasure data about the equipment, status of equipment components, and/orthe equipment's environment. Such data may, for example, include(without limitation) engine revolutions per minute (RPM), engine oiltemperature, engine operation, clutch engagement, ambient temperature,vibration, geographic positioning data, speed, throttle valve position,brake engagement, power-take-off (PTO) system engagement, fuelconsumption, inclination, acceleration, pressure, load, battery status,shock, user input, time, feature operation and status, humidity, nearbyequipment, fuel level, oil level, and/or the like. The equipment datasensor may capture this data periodically and have a non-transitorymemory device, such as a flash memory drive, that stores the captureddata in a time sequence or along with timestamps indicating the momentin time when the data was captured. The equipment data sensor may storethis data at least temporarily until the data communication systemportion of the data collection and communication system 110 can transferthis data to the data management and presentation system 150.

In this regard, the data collection and communication system 110includes a data communication system comprised of one or morecommunication units for obtaining data from the equipment data sensor(s)and communicating the data to the data management and presentationsystem 150 via a global or wide area network such as the Internet and/ora cellular network 105. For example, some embodiments include a basestation 112 that periodically looks for equipment data sensors that comewithin range of its wireless transceiver and then uploads data from theidentified equipment data sensors. For example, the base station 112 maybe located in the fleet owner's garage 106 or other storage unit so thatit captures data from the fleet's equipment data sensors whenever theequipment is returned to the garage 106 at the end of each work day.This base station 112 may have some local memory for temporarily storingsome data, but it may be connected to the Internet so that it cantransfer the data it receives to a remote web server 165 of the datamanagement and presentation system 150. The data collection andcommunication system 110 may also have one or more satellite stations114 that relay data from the equipment data sensors to the base station112. For example, such satellite stations 114 may be installed on thetrucks 107 or trailers that carry the equipment to the worksites. Thecommunication units may also have ID codes associated with them so thatthey may be used to help track the location of equipment in the fleet.For example, a satellite station 114 installed on each truck could helpidentify which equipment is on which truck and a base station 106located in a garage could help identify which equipment is in the garageand when the equipment is removed and/or returned to the garage.

In some embodiments the communication unit may even be a mobile phone orother mobile device that is configured to communicate informationbetween one or more equipment data sensors and the data management andpresentation system 150 using a global mobile network, such as acellular telephone network 105. For example, as illustrated in FIG. 1,the operator 148 of the walk behind mower 144 may hold a mobile smartphone 116 in his pocket that has a short-range transceiver, such as aBluetooth® system or the like. The mobile phone 116 may also have adownloaded fleet management system software application stored in thephone's memory that allows the mobile phone 116 to wirelessly receivedata from the equipment data sensor 124 of the mower 144 using theshort-range transceiver and then relay the data to the data managementand presentation system 150 via the cellular network 105. In this way,it may be possible for the data management and presentation system 150to receive data in real-time or near-real-time and/or, for some users,it may also negate the need for other system-specific communicationsunits. This may be particularly well suited for some owner-operators orhomeowners that would like to utilize the fleet management system 100with less of an investment in communication units like base stations 112and satellite stations 114. In some embodiments, the ID unit 134 may bestored in the mobile phone 134 which may also negate the need for suchequipment as operator data cards or wristbands. In such embodiments, theequipment data sensor 124 may receive the ID code from the mobile phone116 or, alternatively, if the mobile phone 116 is the communicationunit, the mobile phone 116 may associate the ID code stored in the IDunit 134 in the phone 116 with the data the phone 116 receives from theequipment data sensor 124 prior to sending the combined data and ID codeto the data management and presentation system 150. This could alsopotentially reduce the cost of the equipment data sensor 124 since somefunctionality of reading nearby ID units may not be needed in theequipment data sensor 124 in such an embodiment.

As illustrated in FIG. 1, the data collected by the data collection andcommunication system 110 is then communicated to the data management andpresentation system 150 via a network 105. The network 105 may be, forexample, a wide or global area network including the Internet and/or acellular telephone network. The data management and presentation system150 includes a data management server system 162, such as a web server,that receives the data from the data collection and communication system110, stores the data in a database 165, processes the data, and presentsthe data or other data derived therefrom to one or more users in auseful format. For example, the data management server system 162 mayprovide a web portal where users can track information about a fleet'sequipment and operators, including (for example, without limitation)such information as equipment run time, equipment performance, equipmentmaintenance records, equipment repair records, equipment safetyconcerns, equipment productivity, equipment cost, equipment location,equipment use, operator productivity, operator work time, operatormachine handling information, operator performance, operator location,operator safety concerns, operator vibration records, team productivity,job resource requirements, customer information, jobsite information,parts information, contract information, warranty information, libraryresources, and/or the like, as is described in greater detail below. Thedata management server system 162 analyzes the collected data and,utilizing the collected data, provides some or all of the informationlisted above in a format useful to the user.

In some embodiments, the user, such as the fleet owner 101, accesses theweb portal via a personal computing device 170 and a web browsingapplication stored thereon. The data management server system 162provides the information to a secure web page in the format of graphs,charts, tables, and other graphics that help the user to quickly andintuitively see and understand what is being presented. The datamanagement server system 162 also receives user input from the personalcomputing device 170, including input about information to be displayed,user preferences, and additional data about the fleet. In someembodiments, the personal computing device is a mobile phone 172, whichmay be operated by, for example, a team manager 102, an operator, amechanic, or other team member in the field. In some embodiments, themobile phone 172 has a fleet management application stored thereon thatworks with the data management server system 162 to communicateinformation back and forth between the user and the server system 162.

In some embodiments, the data management server system 162 providesdifferent experiences, features, functions, and permissions to differenttypes of users. As mentioned above, some types of user may include afleet owner/manager 101, a team manager 102, an operator, and/or amechanic. Another type of user may be a dealer 103 or other salespersonor the equipment manufacturer. The dealer 103 or manufacturer may alsoaccess the web portal via a computing device or company-owned server andmay have access to a dealer portal or a manufacturer portal configuredto provide information useful to dealers or manufacturers and configuredto allow the dealer or manufacturer to enter information aboutequipment, equipment use, and/or customers that can be used by the datamanagement server system 162, in conjunction with data collected byequipment data sensors, to provide equipment and operator information toa fleet manager, an equipment operator, or other user.

FIGS. 2A and 2B provide a block diagram 200 that illustrates componentsof the fleet management system 100 in more detail, in accordance withsome embodiments of the invention. In this regard, FIG. 2A provides ablock diagram of the data collection and communication portion of thesystem 100, including a data collection system 210 with an equipmentdata sensor 230, a data communication system 260, and an ID unit 250.FIG. 2B provides a block diagram of the data management and presentationportion of the system 100, including a data management server system 270and a client computing device 290.

As used herein, the terms “processing device” and “processor” refer tocircuitry for implementing one or more of the communication and/or logicfunctions of the device within which the processor/processing device isinstalled. For example, the processing devices described herein mayinclude a digital signal processor device, a microprocessor device, andvarious analog to digital converters, digital to analog converters,and/or other support circuits. Control and signal processing functionsof the device within which the processing device is installed areallocated between these circuitry devices according to their respectivecapabilities. The processing device thus may also include thefunctionality to encode and interleave messages and data prior tomodulation and transmission. The processing device can additionallyinclude an internal data modem, a data bus, and/or a power bus forcommunicating data and or power to other components and devices that arecommunicably coupled to the processing device. Further, the processingdevice may include functionality to operate one or more softwareprograms, which may be stored in the memory to which the processingdevice is coupled. For example, the processing device may be capable ofoperating a connectivity program, such as a web browser application. Theweb browser application may then allow the device to transmit andreceive web content, such as, for example, location-based content and/orother web page content, according to a Wireless Application Protocol(WAP), Hypertext Transfer Protocol (HTTP), and/or the like. A processingdevice may include a single processor or a plurality of processors thattogether perform the stated function(s). Where a processing deviceincludes a plurality of processing devices/processors, the processingdevices/processors are generally communicably coupled to each other viaone or more communication devices, but they may not be physicallycoupled to each other; in other words, such processors may be locatedtogether or may be located separate and apart from each other.

The processing devices described herein may be configured to use one ormore transceivers, network interfaces, or other communication interfacesto communicate with one or more other devices or networks. In thisregard, “transceivers” described herein generally include an antennaoperatively coupled to a transmitter and/or a receiver and configured topassively and/or actively send and/or receive data and/or power viaelectromagnetic waves (e.g., radio frequency waves, infrared waves,etc.) and wave modulation. The processing device may, therefore, beconfigured to provide signals to and/or receive signals from thetransceiver. Where the transceiver is configured to communicate with acellular network, the signals may include signaling information inaccordance with the air interface standard of the applicable cellularsystem of the wireless telephone network. The transceiver may also beconfigured to operate in accordance with other communication mechanismsand standards, such as via a wireless local area network (WLAN), aBluetooth® standard, a RFID (radio frequency identification) tagstandard, proprietary wireless communication protocols, and/or othercommunication/data standards and networks.

As used herein, “memory” or “memory device” includes any computerreadable medium (as defined herein below) configured to store data,computer-executable program code (e.g., software), or other information.Memory may include volatile memory, such as volatile Random AccessMemory (RAM) including a cache area for the temporary storage of data.Memory may also include non-volatile memory, which can be embeddedand/or may be removable. The non-volatile memory can additionally oralternatively include an electrically erasable programmable read-onlymemory (EEPROM), flash memory or the like. The memory may be configuredto store any of a number of applications which comprisecomputer-executable instructions/code executed by the processing deviceto implement the functions of the devices described herein. The memorycan also store any of a number of pieces of information/data used by thedevices described herein. Memory or a memory device may include a singlememory device or a plurality of memory devices that together performstore the stated information. Where the memory or memory device includesa plurality of memory devices, the memory devices are generallycommunicably coupled to each other via one or more communication devicesand/or processing devices, but they may not be physically coupled toeach other; in other words, such memory devices may be located togetheror may be located separate and apart from each other.

Referring again to FIG. 2A, a block diagram of an ID unit 250 isprovided, according to an example embodiment of the invention. The IDunit 250 includes a processing device 252 communicably coupled to ashort-range transceiver 264 and memory 254. The memory 254 includes aunique ID code 255 stored therein. Being unique, this ID code 255 can beassociated with a particular operator 204 in order to uniquely identifythe operator. For example, a particular ID code 255 may be associatedwith a particular operator 204 if the operator 204 always or usuallycarries an ID unit 250 with the same ID code 255 stored therein. In someembodiments, a particular ID code 255 may be associated with aparticular operator 204 in a database stored in the memory 276 of thedata management server system 270, described in greater detail below.The code can be any alphabetic, numeric, alphanumeric, or other type ofcode.

The processing device 252 is configured to use the short-rangetransceiver 264 to communicate the ID code 255 to the data collectionsystem 210 at appropriate times using an appropriate wirelesscommunication standard. For example, in one embodiment of the ID unit250, the transceiver 264 comprises a 2.4 GHz antenna that is configuredto work close to an operator's body. In one embodiment, the readingrange for the transceiver 264 is two meters, although other ranges arepossible. In some embodiments, the ID unit 250 is a passive RFID tagwhere the short-range transceiver 264 receives a wireless signal fromthe equipment data sensor 230 and, by virtue of this signal beingreceived in the transceiver's antenna, the ID unit 250 is powered andautomatically responds by transmitting the ID code 255 via a wirelesssignal that is received by the equipment data sensor 230. In otherembodiments, the ID unit 250 comprises a battery (not shown) andactively transmits the ID code 255 either continuously, periodically(e.g., every second), or in response to receiving a signal from anequipment data sensor 230. In some embodiments where the ID unit 250comprises a battery, the ID unit 250 also comprises a motion detector(not shown) and, to conserve battery, is configured to stop transmittingsignals when no motion is detected for longer than a predeterminedamount of time and then resume transmissions when motion is detectedagain. Where the ID unit 250 has a battery, it may be preferable toconfigure the ID unit 250 and the battery so that the battery life is atleast one year.

In one embodiment of the invention, the operator ID unit 250 uses the CC2510 Short Range Device (SRD) RF transceiver provided by Texasinstruments, which is a system on chip transceiver with a built-inmicroprocessor. In one such embodiment, the operator ID unit 250 usesthe CC 2510 which is based on the CC 2500 used for the transceiver inboth the equipment data sensor 230 and the data communication system260. The supported modulation schemes at 250 kbit/s are OOK, 2-FSK, GFSKand OQPSK Offset Quadrature Shift Keying). The frequency range is 2.400GHz to 2.483 GHz allocated as ISM (Industrial, Scientific and Medical).The data rate over the air may be 250 kbit/s. The receiver sensitivitymay be 81 dBm.

As described above, the ID unit 250 may take a variety of forms, but ispreferably a water-resistant, wearable device that can be easily carriedby or attached to an operator 204. For example, the ID unit may be adata card (e.g., a credit-card sized card), a wristband, a chip sewninto the operator's gloves, a key fob, a watch, a necklace, and/or thelike. Although the typical example may utilize RFID technology, otherwireless communication arrangements are conceivable such as, e.g.,Bluetooth® or WiFi. As described above, in some embodiments of theinvention the ID unit 250 is combined with a mobile phone and, as such,the memory 254, processing device 252, and short-range transceiver 264may be those of a mobile phone capable of also performing otherfunctions of the mobile phone. In some embodiments, the ID unit 250 mayalso include a user interface (e.g., a keypad, touch pad, display, LED,or the like) (not shown) for receiving user input and/or providing useroutput. For example, the ID unit 250 may have a keypad for receiving aPIN code or a biometric device for authenticating the operator holdingthe ID unit. In some embodiments, the ID unit 250 may have the ID code255 printed thereon along with the operator's name and/or image or aplace for an operator to write his or her name or attach a picture.

Although only a single ID unit 250 and operator 204 are shown in FIG.2A, it will be appreciated that the fleet management system may comprisea large number of operators and ID units, where each ID unit is carriedby or otherwise associated with a particular operator. In someembodiments, one or more ID units 250 come with the purchase of a pieceof equipment 202 and/or an equipment data sensor 230, but also can bepurchased individually or in packs.

FIG. 2A further provides a block diagram of a data collection system 210comprising an equipment data sensor 230, in accordance with an exampleembodiment of the invention. As illustrated, each piece of outdoor powerequipment 202 in the fleet that is to be monitored by the fleetmanagement system 100 is equipped with a data collection system 210 forcollecting data about parameters related to the equipment and/or theequipment's environment and communicating the collected data to the datacommunication system 260. Each data collection system 210 generallyincludes an equipment data sensor 230 installed on the equipment 202 orotherwise positioned proximate to the equipment 202 during operation ofthe equipment 202. The equipment data sensor 230 may encompass the wholedata collection system 210 or the equipment data sensor 230 may becombined with other components, such as other components of theequipment 202, to form the data collection system 210. Each equipmentdata sensor 230 includes a processing device 232 communicably coupled toone or more transceivers 234, a clock/timer 248, a power source 246,memory 240, and one or more sensors 249.

The memory 240 includes a sensor application 242 stored therein. Thesensor application 242 comprises computer readable program code (e.g.,software, etc.) for instructing the processing device 232 to operate thevarious hardware components and to store, process, and communicate data244. The memory 240 can be any computer-readable medium, such as flashmemory. In one embodiment, the equipment data sensor 230 is configuredto automatically update the sensor application 242, and any firmware inthe other hardware, when in communication with a data communicationsystem 260 that is connected to the data management server system 270.

The processing device 232 executes the sensor application 242 to,amongst other things:

(i) use the transceiver(s) 234 to receive and process wireless signalsfrom one or more ID units 250 or other equipment data sensors;

(ii) use the transceiver(s) 234 to send wireless signals to one or moreID units 250 or other equipment data sensors;

(iii) use the sensor(s) 249 and/or communicate with the equipment'scontrol system 212 to gather other data about the equipment 202 or itsenvironment;

(iv) store data in the memory 244;

(v) use the transceiver(s) to send data to and receive data from thedata communication system 260;

(vi) use the clock 248 to determine absolute or relative time andassociate data with a time; and/or

(vii) use the equipment's user interface 209 to communicate informationto the operator 204.

The memory 240 also, at least temporarily, stores the data 244 collectedby the processing device 232 from the sensor(s) 249 and/or theequipment's control system 212. This data 244 may be comprised ofindividual data packets/packs, where each data packet relates to oneinstance or period of time and includes: (i) sensor data or otherequipment-related data collected at that point in time; (ii) any IDcodes identified from nearby ID units 250 at that point in time; (iii)any identification codes identified from other equipment data sensorsnearby at that point in time; (iv) any identification codes identifiedfrom data communication systems 260 nearby at that point in time; (v) atimestamp indicating the point in time; and/or other data. This data 244may be deleted from the memory 240 after the data 244 is uploaded to adata communication system 260 or the data management server system 270,and/or the data 244 may be deleted after it reaches a certain age or asthe memory 244 reaches certain capacities.

As illustrated, some embodiments of the equipment data sensor 230 arealso uniquely associated with an ID code 245 that can be used by thedata management server system 270 to identify the particular equipmentdata sensor 230 and, thereby, the particular piece of equipment 202 towhich the equipment data sensor 230 is attached or otherwise associated.This equipment ID code 245 may be transmitted to the data managementserver system 270 via the data communication system 260 along with data244. This way the data 244 can be properly associated with a particularpiece of equipment. For example, the equipment ID code 245 may betransmitted at the beginning and/or end of any transmission from theequipment data sensor 230 and/or the equipment data sensor 230 could addthe equipment Id code 245 to each data packet along with the capturedequipment data and any operator ID codes. The equipment ID code 245 mayalso assist with routing communications back to a particular equipmentdata sensor 230 from a data communication system 260 and/or the datamanagement server system 270.

The equipment data sensor 230 also includes one or more transceiver(s)234, which may comprise one or more transmitters and/or receivers. Insome embodiments of the invention, the transceiver 234 is comprised of arelatively short-range transceiver 236 and a relativelylong/medium-range transceiver 238. In such an embodiment, theshort-range transceiver 236 may be used to identify and communicate withnearby ID units 250 and/or equipment data sensors on other equipment,and the long-range transceiver 238 may be used to identify andcommunicate with data communication systems 260 (e.g., base stations112, satellite stations 114, mobile phones 116, or other communicationunits) to send collected data to the data communication systems 260and/or to receive information or updates from the data communicationsystems. In one such an embodiment, the short-range transceiver 236 isconfigured to have a maximum range of approximately two meters and thelong-range transceiver 238 is configured to have a range of at leasttwenty meters. Of course, these ranges are examples and other ranges arepossible. In some embodiments the short-range transceiver 236 and thelong-range transceiver 238 share a single antenna, such as a 2.4 GHzantenna but use different communication protocols, modulationtechniques, and/or amounts of power. In other embodiments a singletransceiver 234 is used to communicate to both the ID units 250 and thedata communication systems 260, but the equipment data sensor 230 may beconfigured to adjust the power to limit the range in which ID units 250are recognized to something less than the range used to communicate withthe data communication system 260.

In addition to communicating wireless signals to and/or from operator IDunits 250 and data communication systems 260, in some embodiments theprocessing device 232 uses the short range transceiver 236 of theequipment data sensor 230 to periodically broadcast an equipment ID code245 over a short range to allow the equipment ID code 245 to be sensedby other equipment data sensors that may be in the nearby area. Also, insome embodiments, the equipment data sensor's transceiver 234communicates with other types of ID units similar to the operator IDunit 250 that uniquely identify equipment that do not have equipmentdata sensors 230 (such as a ID data tag on the bed of a truck in thefleet or in a storage unit or service garage).

The equipment data sensor 230 also includes a clock 248 which may be anytiming device. The clock 248 may keep track of global standard time or arelative time and is used to allow the processing device 232 to performactions, such as capturing data from the sensors 249 or transmittingsignals using the transceiver 234, in regular intervals. The clock 248also allows the processing device 232 to store collected data in timesequence or with a timestamp that shows when the data was collectedrelative to when other data was collected and, in some embodiments,relative to global standard time or another standardized temporalindicator.

The processing device 232 of the equipment data sensor 230 is configuredto communicate with one or more sensors to collect data about theequipment, operation of the equipment, and/or the equipment'senvironment. In some embodiments, the equipment data sensor 230 hassensors 249 built into the equipment data sensor 230, itself. In fact,in some embodiments the equipment data sensor 230 is entirelyself-contained, and in some cases self-powered, and does not require anyhard-wired connections to any electrical components of the equipment202. Such an embodiment may make installation of the equipment datasensor 230 easier and more universal, particularly if the installationoccurs after manufacturing of the equipment 202.

In other embodiments, in addition to or as an alternative to havingsensors 249 incorporated into the equipment data sensor 230, theprocessing device 232 may be configured to collect data from one or moresensors 222 that are built into the equipment 202 apart from theequipment data sensor 202. For example, the equipment data sensor 230may be configured to obtain and store in memory 240 the status of anoperator presence sensor typically built into the seat of a riding lawnmower to identify whether an operator is seated in the seat of theriding lawn mower. In this regard, the processing device 232 may becommunicably coupled (e.g., coupled by a wired or wireless connection)to an equipment control system 212 of the equipment 202 to “tap into”the equipment's electrical system and receive data from the equipmentsensors 222. As such, some embodiments of the equipment data sensor 230include a wiring harness arranged to exhibit connecting ports forproviding connection between the processing device 232 of the equipmentdata sensor 230 and the equipment control system 212 and/or variousexternal sensors 222 or switches 224. The equipment control system 212may include a processing device (e.g., one or more processors, a databus, circuits, etc.) for communicating with the equipment's sensors 222.It should be appreciated that the equipment sensors 222 may includeswitches 224 where the sensed data from a switch 224 comprises thestatus of the switch 224 (e.g., on, off, etc.). The equipment controlsystem 212 may also be communicably coupled to the equipment powersource 246 and the equipment user interface 209 and, therefore, in someembodiments the processing device 232 of the equipment data sensor 230can receive and store information about user inputs entered through theequipment user interface 209 and provide user output via the equipmentuser interface 209 (e.g., user output that may originate from the datamanagement server system 270).

In some embodiments, the sensors 249 and/or 222 that are communicablycoupled to the processing device 232 of the equipment data sensor 230include one or more of the following: GPS receivers, RPM sensors (e.g.,RPM-sensing antennas), three-axis accelerometers or otheraccelerometers, electro-mechanical switches, inclinometers,thermocouples or other temperature sensors, proximity sensors, fluidlevel sensors, pressure transducers or other pressure sensors, moisturesensors, motion detectors, magnets and magnetic field sensors,Hall-effect switches, RF antennas, infrared sensors, lasers, shocksensors, speed sensors, vibration sensors, and/or other sensors. In someembodiments, the equipment data 244 collected and stored by theequipment data sensor 230 includes one or more of the following: GPS orother location data, engine RPM, component (e.g., cutting blades) RPM,accelerations, orientation, incline, ambient temperature, enginetemperature, transmission temperature, component temperature, nearbyequipment ID codes, nearby communication system ID codes, throttlestatus, PTO status, brake status, clutch status, user input commands,switch statuses, fuel consumption, fuel level status, oil level status,battery level status, voltage, electrical current, velocity, operatorpresence in a seat or other operator station, heading, run time,ignition status, vibration, shock, tire level, tire condition,differential locking, wheel spinning, emissions, wheel slipping,humidity, force, moisture, pressure, altitude, tampering, equipmenthatch opening or closing, user input, component replacement, and/orother parameters/metrics about the equipment's status, use, operation,and/or environment.

For example, in some embodiments of the equipment data sensor 230, thesensor(s) 249 include sensors for sensing the engine speed, the PTOspeed, and/or the work performed by the engine. For example, the enginespeed may be sensed by an RPM sensor for sensing (exactly orapproximately) the revolutions per minute (RPM) of the motor shaft,which may be the crankshaft of an internal combustion engine or theshaft driven by an electric or hybrid engine. The PTO speed may besensed by the RPM of a PTO shaft or pulley. The engine workload may besensed by some ratio of the actual engine speed, throttle position,reference engine speed, and/or PTO speed.

According to one embodiment of the invention where the equipment datasensor 230 is arranged to collect information regarding the RPM of theequipment's internal combustion engine, the equipment data sensor 230may include an “intelligent sensor” in the form of a registration unitmounted around or adjacent to the ignition cable. This registration unitis capable of sensing and storing electrical impulses that arise at eachignition, meaning the RPM may be retrieved since increased engine speedresults in more frequent ignition pulses.

In another embodiment described in detail below with reference to FIGS.3A, 3B, 4A, and 4B, the RPM sensor comprises a RPM antenna that islocated some distance (e.g., between 1 and 40 centimeters) away from theignition cable that is configured to determine engine RPM by sensingelectromagnetic waves generated by equipment components that vary withthe RPM of an internal combustion engine (e.g., waves generated by theelectrical ignition pulses that arise in the ignition circuit and thatchange based on the engine speed). This embodiment may have an advantageover other embodiments because it may be more cost effective and permitssensing of engine RPM from a distance away from the ignition cable,senses the RPM passively, provides for easier installation, and avoidsinterfering with the ignition cable or other engine components since itdoes not require that the RPM sensor be hardwired into electrical orengine systems of the equipment 202. Hereby it may also be possible toregister and store when the engine is started as well as when it is shutdown, and moreover the RPM-levels between start and shut down. In someembodiments where such an RPM antenna is used and actual engine RPM maynot be needed or cannot be obtained, such as for some types of ridingmowers or some other vehicles, then an adapter/sensor combination may beattached to equipment to sense one or more other characteristics aboutthe equipment or the equipment's use and convert the sensed informationinto electromagnetic pulses that simulate ignition circuit pulses.Different “RPM” values can be used to communicate different informationaccording to some predetermined rules. For example, the adapter couldcreate electromagnetic pulses consistent with an engine RPM of 500 toindicate to the equipment data sensor 230 (via the RPM antenna)something like “engine on and PTO not engaged” and pulses consistentwith an engine RPM of 1000 to indicate something like “engine on and PTOengaged.” In this way, the same equipment data sensor 230, such as theuniversal equipment data sensor described with respect to FIGS. 3A, 3B,4A, and/or 4B, could be used for a greater number of equipment types andto sense a greater variety of data according to the particular needs ofthe user and requirements or limitations of the equipment type or itsenvironment.

In another embodiment, the RPM sensor of the equipment data sensor 230comprises at least one intelligent powered sensor that is configured tobe self-energized and, in some cases, power the rest of the equipmentdata sensor 230. Specifically, in some embodiments the RPM sensor of theequipment data sensor 230 includes an inductor powered byelectromagnetic energy from the engine of the equipment 202. A magnet isadded to one portion of the flywheel of the engine of the equipment 202.The RPM sensor is then located in such a way that passing magneticfields (created by the magnet as the flywheel turns and the magnetpasses the sensor) can be sensed and registered by the RPM sensor (e.g.by means of a RPS sensor comprising metal portions). The RPM sensor thentransforms these magnetic fields into electrical signals which can befurther transmitted to the processing system 232 of the equipment datasensor 230 and used thereby to estimate RPM and engine start and stop,and/or to power the equipment data sensor 230 (including charge any ofthe its batteries). A similar setup could be used to sense the speed(e.g., RPM) of and receive power from other rotating/moving devices onthe equipment 202, such as a PTO shaft, a belt, a pulley, a cuttingelement, and/or the like, by similarly attaching a magnet to therotating/moving component to be sensed. Other sensors may also be usedto sense RPM or other speed indicators of an engine or component, suchas Hall-effect switches located near the moving component.

In some embodiments, the equipment control system 212 is configured tocontrol fuel supply to the internal combustion engine of the machine,and the equipment data sensor 230 is communicably coupled to theequipment control system 212. On some such embodiments, the equipmentdata sensor 230 may receive power from this connection. In someembodiments the equipment control system 212 may be arranged to controlthe carburetor of the equipment 202 and include: (i) a throttle positiondetecting mechanism for sensing the position of the throttle valve;and/or (ii) a fuel valve mechanism for controlling the fuel supply tothe engine. The equipment data sensor 230 may be communicably coupled tothe throttle position detecting mechanism (e.g., via the equipmentcontrol system 212) at least for sequentially obtaining valuesrepresenting the position of the throttle valve. The equipment datasensor 230 may also be an integrated part of the equipment controlsystem 212 and vice versa. Such an arrangement may allow for use of theequipment control system 212 for adjusting the air/fuel mixture to theengine for current conditions, thereby lowering the fuel consumption,and at the same time being able to use the equipment data sensor 230 forregistering and storing information about to what extent the equipmentcontrol system 212 has been activated during the running of a machine.Thus, in embodiments where the equipment 202 includes an equipmentcontrol system 212 for, for example, controlling a fuel supply to aninternal combustion engine of the machine, the equipment data sensor 230can be configured to receive values of at least one parameter from theequipment control system 212. One such parameter could be the throttleposition which, taken together with the RPM, can be used for renderingan estimated value of load and/or fuel consumption.

In some embodiments, the equipment control system 212 includes anignition module for controlling the ignition timing of an internalcombustion engine of the equipment 202. In such embodiments, theequipment data sensor 230 may be preferably integrated with the ignitionmodule or capable of being attached to the ignition module, and saidignition module may be arranged to control the ignition timing of aninternal combustion engine of the machine. In such an embodiment, theequipment data sensor 230 may be connected to the ignition system andmay be arranged to become activated when the ignition system is switchedon.

Powering of the equipment data sensor 230 can be achieved in differentways, some of which have been described above. According to someembodiments, the power source 246 of the equipment data sensor 230comprises one or more batteries. In some such embodiments, the batteriesare rechargeable batteries and, in some embodiments, are charged byelectromagnetic induction generated by moving magnets, e.g. placed onthe engine flywheel of the equipment 202. An example of electromagneticconverting means arranged to convert magnetic energy into electricalenergy is described in U.S. Patent Application Publication No.2011/0095215, which is hereby incorporated by way of reference and whichis commonly owned by an assignee of the present application. Thus thebatteries of the equipment data sensor 230 may be charged while theequipment 202 is running by this induction method or by otherwiseconnecting the batteries to the equipment's power source 208 (battery,electrical circuits, engine, solar cell, generator, etc.).

In some embodiments, the equipment data sensor 230 is configured totransmit information about battery status (e.g., voltage) to the datamanagement server system 270 so that any worn-out battery can beidentified by the fleet management system and an appropriate alert canbe sent by the data management server system 270 to a person responsiblefor changing the battery. Furthermore, the equipment data sensor 230 mayalso be configured to collect, store, and communicate informationrelated to the voltage of the ID unit 250 (e.g., via the power of thewireless signal detected by the equipment data sensor 230 when it'sknown how far way the ID unit 250 is from the sensor 230, for example,by determining that the ID unit 250 is carried by the actual equipmentoperator) whereby battery status of a battery in the ID unit 250 (inembodiments where there is such a battery) can be monitored by the fleetmanagement system 100 and worn out batteries promptly replaced by usersof the system 100.

In sum, it is to be understood that the equipment data sensor 230 mayrefer to any type of unit which provides one or more functions, namelyto: (i) obtain/collect and store values of parameters associated with apiece of equipment 202 or the operation or environment thereof, and,optionally (unless expressly claimed otherwise) (ii) receive and storeincoming operator ID-codes. In this regard, the equipment data sensor230 typically includes a central processing device 232 arranged tosequentially obtain and store values of said at least one parameterduring operation of the machine, whereby a wide variety of informativedata related to a given moment in time may be achieved. The obtainedparameters and any ID codes are stored together in memory 240 in arespective data packet. Each data packet may also include a timestamp sothat the equipment data sensor 230 may collect various data in datapackets containing information about, for example, the operator and anequipment parameter together with a timestamp whereby the collectedinformation is correlated with the period or point in time when theinformation was collected or stored.

It is to be understood that the equipment data sensor 230 and thecomponents described herein may be constituted by various sub-units(e.g. different types and number of sensors depending on what type ofdata is to be collected) as well as it can be mounted into the equipment202 in many different ways, e.g. depending on the type of engine(combustion engine or electrical engine) and type of equipment 202(e.g., wheeled, handheld, etc.), and can be powered in various ways(e.g. with separate batteries or via the engine of the powered machine).In situations where the equipment 202 is powered by an electric motor,the equipment data sensor 230 may have another composition compared tosome of the previously-described embodiments for equipment having acombustion engine. For instance, for electric equipment, the equipmentdata sensor 230 or a portion thereof may be an integrated part of theelectric motor control system, such as a data chip on a printed circuitboard.

FIG. 2A also provides a block diagram of a data communication system 260in accordance with some embodiments. The data communication system 260may be, for example, the base station 112, the satellite station 114,the mobile phone 116, or other communication unit or combination ofcommunication units described with reference to FIG. 1. The datacommunication system 260 is configured to relay information collected byone or more equipment data sensors 230 to the data management serversystem 270 via network 206. The data communication system 260 generallycomprises a processing device 262 communicably coupled to one or moretransceiver(s) 264, a network interface 265, and a memory 266. Theprocessing device 262 uses the network interface 265 and the transceiver264 in accordance with computer-executable instructions of the collectorapplication 268 stored in the memory 266. In some embodiments, theequipment data sensor 202 periodically looks for a data communicationsystem 260 so that when the equipment 202 is brought within thebroadcasting range of the data communication system 260 the equipmentdata 244 (including any operator ID codes 255, equipment ID code 245,and captured equipment data) is submitted thereto by, for example, theequipment data sensor 230 wirelessly transmitting the information in theform of the previously-described data packets. In other embodiments, theequipment data sensor 202 may be configured so that it only looks for adata communication system 260 when the engine is shut down. Theequipment data sensor 202 may determine, for example, that the engine isshut down when no ignition signals are received through the RPM sensoror by some other communication with the equipment's control system 212,user interface 209, or power source 208.

Each data communication system 260 may receive and store informationfrom at least one, and perhaps from more than one, equipment data sensor230 located within broadcasting range. The data communication system260, which may temporarily store the data 244 in the memory 266,thereafter uses the network interface to transmit the data 244 (in theform of the digital data packets) to the data management server system270. The data management server system 270 is thereby provided withinformation in the form of equipment and operator data, and iscontinuously/periodically updated about the status of a fleet inoperation as new information from the data communication system 260 isreceived.

As illustrated in FIG. 2A, the memory 266 of the data communicationsystem 260 may, in some embodiments, include an operator ID code 255and/or a communication system ID code 269. The communication system IDcode 269 may be uniquely associated a particular data communicationsystem 260 and then used by the data management server system 270 toidentify the particular data communication system 260. This ID code 269may be useful to the data management server system 270 for: (i)identifying the source of data generally; (ii) identifying problems witha data communication system 260 (iii) tracking the location of one ormore pieces of the equipment (e.g., by associating the location of theequipment 202 with a known location of the data communication system 260at the time of the communication between the equipment's data sensor 230and the data communication system 260); (iv) identifying the fleet owneror account associated with certain incoming data; and/or (v) routingcommunications back to a particular data communication system 260 and/orequipment data sensor 230 from the data management server system 270.This communication system ID code 269 may be transmitted to the datamanagement server system 270 along with data 244. For example, thecommunication system ID code 269 may be transmitted at the beginningand/or end of any transmission from the data communication system 260and/or the data communication system 260 could add the equipment ID code269 to each data packet along with the captured equipment data and anyoperator ID codes and equipment ID code.

As described above, in some embodiments of the fleet management system100 where the data communication system 260 comprises a mobile device116 that can be assumed to be specific to and carried by a particularoperator, the data communication system 260 may also function as an IDunit 250. Therefore, in such embodiments, the memory 266 may alsocontain an operator ID code 255. This may be transmitted to theequipment data sensor 230 using the transceiver 264 in much the sameway(s) described above with reference to the ID unit 250 or,alternatively, it may be added to the data 244 as the data 244 passesthrough the data communication system 260 on its way to the datamanagement server system 270.

The network 206 may be any data communication network. In someembodiments, the network 206 comprises a global area network such as theInternet and/or a cellular telephone network. However, the network 206may also comprise a local area network (LAN) or a wide area network(WAN). The network 206 may comprise one or more wireless networks and/orone or more wired networks.

In one embodiment of the invention, the network 206 comprises theInternet and the data communication system's network interface 265comprises an Ethernet interface and is configured to communicate withthe data management server's network interface 272 using HypertextTransfer Protocol (HTTP), Transmission Control Protocol/InternetProtocol (TCP/IP), Dynamic Host Configuration Protocol (DHCP), and/orDomain Name System (DNS) protocol. In another embodiment of theinvention, the network 206 comprises a mobile communication network andthe data communication system's network interface 265 comprises one ormore known cellular/mobile antennas and is configured to communicatewith the data management server's network interface 272 using one ormore known cellular/mobile communication and data formatting protocols.

The data management server system 270 is configured to receive the data244 including the various ID codes from a plurality of equipment datasensors 230 via a plurality of data communication systems 260 andprocess the data 244 to provide the data and other data based thereon ina useful form and/or to provide one or more services for users of afleet management portal that is hosted on the network 206 by the datamanagement server system 270. For example, in some embodiments, the datamanagement server system 270 provides a fleet management service fornumerous fleet owners across the world. In some embodiments, portions ofthe fleet management portal are geared to fleet owners while otherportions may be targeted to operators, dealers, manufacturers, and/orother users. Furthermore, in some embodiments of the invention, the datamanagement server system 270 can use the data it receives to provideother useful data back to the equipment data sensor 230 for presentationto an operator of the associated equipment 202 via the equipment userinterface 209 and/or for use by the equipment control system 212.

The data management server system 270 generally includes a processingdevice 274 communicably coupled to a network interface 272 and memory276. These components may be located on a single network server ordistributed across several coupled or independent servers. The networkinterface 292 is configured to connect to the network 206 andcommunicate via the network's protocols, such as HTTP and/or otherInternet or mobile network protocols. As such, depending on theembodiment, the network interface 292 may include, for example, a webmodem and/or some other type of data transceiver.

The memory 276 includes a fleet management server application 278comprising computer-executable code that, when executed by theprocessing device 274 instructs the processing device 274 to perform thevarious functions of the data management server system 270 describedherein. For example, the fleet management server application 278instructs the data management server system 270 to receive data from thenetwork 206, store the data, processes the data, provide feedback to thedata communication systems 260 and equipment data sensors 230, and/orhost a fleet management web portal or mobile application that presentsusers 203 with the fleet and operator data in the form graphs, tables,charts, numbers, graphics, images, audio, alerts, and/or the like in thecontext of a web page or mobile application and/or via emails, textmessages, printouts and/or other communication formats. In this regard,embodiments of the fleet management server application 278 may includecomputer-executable program code that, in combination with a processingdevice capable of executing the code, provides: (i) a receiver module278A for receiving data from the data communication systems 260 (e.g.,the HTTP Posts) via the network interface 272 and storing the data 282in the fleet management system database 280; (ii) a parser module 278Bfor taking the data 282 received by the receiver module 278A, which inthe native format as created by the equipment data sensor 230 or otherdevices in the data collection system, and parses and translates thedata 282 for eventual conversion and presentation in a fleet managementportal; and (iii) a converter module 278C for converting and enrichingcollected data 282 before it is presented in a fleet management portalas processed fleet data 284 (e.g., performing data conversions,performing lookups like warning levels, rules, calculated performanceindicators, equipment information, baselines, references, etc., andcalculating ratios, totals, averages, etc.). In some embodiments, thefleet management server application 278 also includescomputer-executable program code that, when executed by the processingdevice 274 provides over the network 206 different versions of a fleetmanagement portal, such as a user portal 278D intended for fleet owners,fleet managers and/or equipment operators, a dealer portal 278E intendedfor dealers or other sales personnel, a manufacturer portal 278Fintended for equipment manufacturers, and/or a service provider portal278G intended for the provider of the fleet management system or theprovider's service personnel.

The memory 280 also includes, as mentioned above, a fleet managementsystem database 280 that stores: (i) the collected fleet data 282received from the equipment data sensors 230 via the data collectionsystems 260; (ii) processed fleet data 284 which includes data derivedby the data management server system 270 from the collected fleet data282; (iii) fleet owner account data 286 which includes data about thefleet owners, their accounts, and their account preferences; and (iv)dealer account data 288 which includes data about the equipment dealers,their products and services, equipment parts, the dealers' accounts, andtheir account preferences.

Users 203 of the fleet management system 100, who may be fleet owners,equipment dealers, equipment repairmen, homeowners, operators,customers, and/or others, can access the fleet management portal using aclient computing device 290. The client computing device 290 may be, forexample, a personal computer or a mobile smart phone. As illustrated inFIG. 2B, the client computing device 290 generally includes a processingdevice communicably coupled to a network interface 292, a user interface293, and memory 295. The network interface 292 is configured to connectto the network 206 and communicate with the data management serversystem 270 via the network's protocols. As such, depending on theembodiment of the client computing device 290, the network interface 292may include, for example, a web modem and/or a cell phone transceiver.The memory 295 includes a web browsing application 296 and/or a fleetmanagement client application 297 that are executed by the processingdevice 291 to allow the user to access, view, and interact with thefleet management portal via the network 206. Information provided viathe fleet management portal by the data management server system 270 is,in some embodiments, displayed on the display 294 or otherwise providedthrough other user output devices of the client computing device 290.The user 203 interacts with the fleet management portal and providesinput to the data management server system 270 using one or more userinput devices of the client computing device's user interface 293.

Universal Equipment Data Sensor with RPM Sensor

FIGS. 3A, 3B, 4A, 4B, and 5 provide schematic and electrical diagrams ofan example equipment data sensor 300 including an example engine RPMsensor 550, according to some embodiments of the invention. Thisparticular example of the equipment data sensor 230 described withreference to FIG. 2A is referred to herein as the “universal equipmentdata sensor” 300 because it is configured so that, in some embodimentsof the fleet management system, it may be used across all or at leastmany different types of outdoor power equipment in the fleet with littleor no modification to the sensor and/or the equipment. However, theuniversal equipment data sensor 300 may or may not be completely“universal” depending on the embodiment. Furthermore, elements of theequipment data sensor and engine RPM sensor described with reference toFIGS. 3A, 3B, 4A, and 4B may be used in other embodiments of theequipment data sensor 230 and are not necessarily limited to theuniversal equipment data sensor 300.

FIGS. 3A and 3B provide schematic diagrams showing a possibleconstruction and layout of the universal equipment data sensor 300, inaccordance with one embodiment of an equipment data sensor 230.Specifically, FIG. 3A illustrates a top view of the sensor's printedcircuit board (PCB) 310, which in one embodiment is between thirty andforty millimeters wide and between thirty and forty millimeters long.FIG. 4A is an electrical diagram 520 showing an example embodiment ofthe electrical circuits of the universal equipment data sensor 300 or,more generally, the equipment data sensor 230 and components thereof.

Referring again to FIG. 3A, the PCB 310 comprises a component area 312having a microprocessor 350 (which, in this embodiment, is part of theprocessing device 232 shown in FIG. 2A) located therein. Themicroprocessor 350 is operatively coupled to a radio 325 (which, in thisembodiment, is part of the transceiver 234 of FIG. 2A), a memory device330 (which, in this embodiment, is part of the memory 240 of FIG. 2A), a26 MHz crystal oscillator 349 (which, in this embodiment, is part of theclock 248 of FIG. 2A), a 32 KHz crystal “wake-up” oscillator 345 (which,in this embodiment, is part of the clock 248 of FIG. 2A), a plurality ofcapacitors 360 (which, in this embodiment, are part of the processingdevice 232, the RPM sensor 249, and perhaps other components havingcapacitors in their circuits of FIG. 2A), and an opto-coupler 390(which, in this embodiment, is part of the processing device 232 of FIG.2A), which are all also located in the component area 312 of the PCB310. The microprocessor 350 is also operatively coupled to a 2.4 GHzantenna 320 (which, in this embodiment, is part of the transceiver 234of FIG. 2A) and a RPM antenna 380 (which, in this embodiment, is part ofa RPM sensor 249 of FIG. 2A) located on the PCB 310 in the areasurrounding the component area 312. It will be appreciated that,although the only sensor shown in FIGS. 3A and 3B is an engine RPMsensor, other embodiments of the universal equipment data sensor 300 mayhave other sensors incorporated therein and/or may receive data fromother sensors located elsewhere on the equipment.

In one embodiment, the microprocessor 350 comprises an xmega256microprocessor provided by Atmel Corporation. The microprocessor 350 maybe a low power, high performance 8/16-bit AVR microcontroller featuringan 8 KB boot code section, 16 KB SRAM, 4096-Byte EEPROM, external businterface, 4-channel DMA controller, 8-channel event system, and up to32 MIPS throughput at 32 MHz. FIG. 4A shows an electrical diagram of anexample MicroControl Unit (MCU) circuit 525 which may comprise themicroprocessor 350. Other microprocessors may be used in addition to orin place of this particular example.

The memory of the universal equipment data sensor 300 may include memoryin the microprocessor for storing computer-executable code, such as a256 KB self-programming flash program memory, and the memory device 330for storing collected data 244 and/or additional computer-executablecode. In one embodiment, the memory device 330 is a 32 MB flash memorydevice. FIG. 4A shows an electrical diagram of an example memory circuit522 which may comprise the memory device 330. Other memory devices maybe used in addition to or in place of these particular examples.

The radio 325 and the 2.4 GHz antenna 320 form the RF transceiver 234 ofthe universal equipment data sensor 300. This radio 325 is configured touse the 2.4 GHz antenna 320 to wirelessly communicate with both the IDunits 250 and the data communication system 260. In one embodiment, theradio 325 comprises the CC2500 radio provided by Texas Instruments. Inthis regard, the radio 325 may be a low-cost, 2.4 GHz transceiverdesigned for very low-power wireless applications and having a circuitintended for the 2400-2483.5 MHz ISM (Industrial, Scientific andMedical) and SRD (Short Range Device) frequency band. The radio 325 maybe integrated with a baseband modem that supports various modulationformats and has a configurable data rate up to 500 kBaud. The radio 325works with the microprocessor 350 to perform packet handling, databuffering, burst transmissions, clear channel assessment, link qualityindication and wake-on-radio. FIG. 4A shows an electrical diagram of anexample transceiver 526 which may comprise the radio 325 and the antenna320. Other radios and antennas may be used in addition to or in place ofthese particular examples.

Since accurate start-up and general system timing is desired in theuniversal equipment data sensor 300, the sensor 300 comprises a 32 KHzcrystal oscillator 345 and a 26 MHz crystal 340. The 32 KHz crystaloscillator 345 is the “wake-up” oscillator and is used as a wake-uptimer. The 32 KHz crystal oscillator 345 is calibrated by the 26 MHzoscillator, which controls start-up of components and general systemtiming. These crystals may be quartz crystals. FIG. 4A shows anelectrical diagram of an example clock circuit 521 comprising aReal-Time Clock (RTC) circuit which may include the crystal oscillator345 and/or crystal 340. Other crystals and oscillators may be used inaddition to or in place of these particular examples.

The universal equipment data sensor 300 may also include otherelectrical components for managing power, safety, and/or performance ofthe sensor 300 such as one or more capacitors 360 for regulating powerand an opto-coupler 390 (also sometimes referred to as an opto-isolator)for preventing damage to the other electrical components caused byrapidly-changing voltage or high voltage differentials across thecircuit.

The universal equipment data sensor 300 also includes a RPM sensor forsensing the RPM of the equipment's engine. In this embodiment, the RPMsensor comprises an RPM antenna 380 that senses electromagnetic wavescreated by pulses in the equipment's ignition cable when the engine isrunning. The pulses and frequency of the electromagnetic waves vary withthe engine's RPM and, therefore, can be used to sense the engine's RPM.

In one embodiment, the sensor 300 is capable of using the RPM antenna380 to wirelessly sense engine RPM up to forty centimeters away from theignition cable. As such, placement of the universal equipment datasensor 300 on the equipment is somewhat flexible. Where all of thesensors (such as the RPM sensor) used by the universal equipment datasensor 300 to collect data about the equipment are contained within thePCB 310 as shown in this example, and where the sensor 300 has its ownpower source such as a battery, the universal equipment data sensor 300can be installed on a variety of machines with relative ease. In oneembodiment, where a battery is used to power the sensor 300, the batteryand power usage of the sensor 300 may be configured such that the 1200hour-per-year user may have to replace the battery every year, while a600 hour-per-year user may only have to replace the battery every otheryear.

FIG. 4A shows an electrical diagram of an example engine RPM sensorcircuit 550 which may comprise the antenna 380. FIG. 4B provides acombination block diagram and electrical diagram illustrating the engineRPM sensor circuit 550 and how it functions in more detail according toone embodiment. As illustrated in FIG. 4B, for equipment 202 where theequipment power source 208 includes an internal combustion engine 216,the equipment control system 212 will generally include an ignitionmodule 213 electrically coupled to one or more spark plugs 215 in theengine 216 via an ignition wire 214. The illustrated embodiment of theengine RPM sensor 550 senses engine RPM by sensing electromagneticpulses/waves 555 emanating from the ignition wire 214 whenever thesignal changes in the wire corresponding to a spark being generated in aspark plug 215. This particular solution takes no energy from theignition system and may allow for wireless sensing of engine RPM from avariety of locations on or around the equipment 202.

More particularly, the input to the RPM sensor unit 550 is an area onthe printed circuit board of the equipment data sensor 230 that works asan antenna 580 with enough area to pick up the electric field 555generated by the ignition circuit (e.g., the ignition wire 214). Theantenna 580 is electrically coupled to the rest of the RPM sensorcircuit 550, which in this embodiment includes two very-low-powerintegrated circuits 582 and 590 and two inverters 560 and 570 (onehaving a Schmitt trigger input).

Together with the other components, the current consumption of this RPMsensor 550 may be a maximum of approximately 0.1 μA when the engine isturned off, and the current may vary, according to the RPM, between 0.5and 5 μA when the engine is on. Higher RPM results in higher currentconsumption. In some embodiments, all electronics in the RPM sensor 550work with a power supply at approximately three volts.

The first circuit 582 located electrically between the antenna 580 andthe first inverter 560 contains a capacitor 584 and a resistor 586,which together work as a filter and set the input impedance. The filter584 protects against noise from internal high frequencies in theequipment data sensor 230 and external sources like mobile phones or thelike. At the same time the filter 584 integrates the RPM-pulse fromevery ignition. When the engine is turned off the inverter input for thefirst inverter 560 is held low “0”=>0 volt, because the resistor 586 isconnected to ground. Consequently, the output from the inverter 560 ishigh “1”=>3 volts. When a RPM-pulse occurs on the input via the antenna580 with a peak level passing half the supply voltage, the inverteroutput of the first inverter 560 changes from “1” to “0”. Thisfunctionality also protects against generated noise levels on the inputbelow half the supply voltage.

The second circuit 590 located electrically between the first inverter560 and the second inverter 570 has two functionalities. First, when theRPM—pulse sensed by the antenna changes the output of the first inverter560 from “1” to “0”, it quickly discharges a capacitor 594 in the secondcircuit 590 through a diode 592 and resistor 596, which lowers thevoltage on the input to the second inverter 570. When that voltagepasses the lower Schmitt trigger hysteresis voltage, then the output onthe second inverter 570, and hence the input to the processing device232, goes high “1”. Second, when the RPM—pulse ends and the output fromthe first inverter 560 goes “1” high, then the second capacitor 594 ischarged slower through the second resistor 598. And when that voltageover the second capacitor 594 passes the higher Schmitt triggerhysteresis voltage, then the output on the second inverter 570 and theinput to the processing device 232 goes low “0”. Consequently, oneRPM—pulse is generated to the processing device 232 enabling theprocessing device to count the RPM pulses. The slower charge of thesecond capacitor 594 increases the output pulse length so it covers andminimizes double pulse detection. This “disable window” does not detectany pulse after the first detection for 270 uS.

In some embodiments, the equipment data sensor 520 has the capability tosample and process engine RPM data within the range of 0 and 15,000 RPM.As described above, this may be done by registering signal changes inthe machine ignition cable, but other RPM sensors are also possible. Inone embodiment, the equipment data sensor 520 stores samples in sessionsof 15 minutes in order to preserve memory in an effective way. Eachsession may be stored as a histogram containing the number of samplesper RPM interval over a particular period of equipment operation.

In some embodiments, the RPM sensor 520 samples every 5 ms (200 Hz).During ten seconds it will collect the samples without the help of theprocessing device 525 and all the sampling will be achieved by the anevent system, sampling timer. During the RPM sampling the microprocessor525 may be in idle mode allowing the peripherals to continue working.The microprocessor 525 and peripheral clock may be driven by theexternal 32,768 KHz crystal and therefore the current during thesampling may be as low as 97 μA. Once the raw RPM data is stored inmemory 522, it is processed by the microprocessor 525 to assign the datain the correct RPM segments. These segments will create the RPMhistogram that may be used by the data management server system 270.

When it is time to process the data, the microprocessor 525 andperipheral clock 521 will be changed to 24 Mhz allowing the equipmentdata sensor 520 to process the data fast. (e.g., 136 ms). Thisprocessing will take place once every 10 seconds.

Referring again to the electrical diagram of the equipment data sensor520 illustrated in FIG. 4A, battery 523 (an example of power source 246)is shown. In the illustrated embodiment, it may be important to have asmall battery dimension, but the drawback is low current capability. Assuch the battery may be supported by a large capacitor bank for highcurrent pulse capability. Voltage: 3.0-3.6 V; Peak current capacity: <20mA; Battery capacity: >500 mAh; Type: CR2450 or better.

Other sensors 527 are also included in this embodiment of equipment datasensor 520, including a temperature sensor 528 and a vibration/tiltsensor 529. In the illustrated embodiment of the temperature sensor, theapproximate machine temperature data is obtained from a commonNTC-resistor mounted on the printed circuit board of the equipment datasensor 520. For better linearity in the lower region a bleeder resistoris used (parallel connected). The equipment data sensor also uses theRTC 521 to keep track of time and therefore it can time stamp everyevent when it happens. This data is stored in non-volatile memory 522.In some embodiments, the equipment data sensor 520 uses the temperaturesensor 528 to log the surrounding temperature during engine-on time andtwenty minutes thereafter.

An omnidirectional tilt/vibration sensor 529 is also used in the exampleequipment data sensor 520. When in rest, the tilt/vibration sensor 529is normally open, giving a true zero quiescent current. An averagingfilter keeps the sensor signal in rest until several movements occur,resulting in low CPU activity and power consumption. Due to low powerconsumption the circuit resistors have very high resistance. Thetilt/vibration sensor 529 on is used during engine OFF mode, to identifytwo major states (engine OFF state is when data logging is not activewhile a base station search or a data transfer is active): (i) activebase station search mode (when the vibration sensor is triggered); and(ii) passive base station search mode (when the vibration sensor is nottriggered).

The example equipment data sensor 520 also includes LEDs and alightsensor circuit 530. When the user installs the battery for thefirst time or has just replaced the battery, the equipment data sensor520 will enable its indication LED's. The purpose of the LEDs is to seethat the main functionality of the equipment data sensor 520 is working.These indication LEDs will be active for only 10 minutes and then theywill be turned off down. There are three LEDs in this embodiment thatindicate different functionalities: (i) LED 1 (green)—CommunicationLED—this led will light up every time the equipment data sensor 520sends a wireless packet to the Base Station; (ii) LED 2 (red)—TiltSensor LED—this led will indicate when the tilt sensor is activated and,therefore, when the sensor is moved then this LED should light up for200 ms; and (iii) LED 3 (yellow)—RPM LED—this LED should light up everytime the equipment data sensor 520 is positioned next to a handheldequipment engine. It will constantly be lighted as long as the engine ison and the sensor is in an appropriate sensing distance (less than 20 cmfrom the engine)

The example equipment data sensor 520, also includes debug pins 531comprised of a JTAG interface that is available for debugging andsoftware download.

In the example equipment data sensor 520, the memory 522 includes 256 kBof In-System Self-Programmable Flash, 4 kB EEPROM, and 16 kB InternalSRAM.

FIG. 3B provides a schematic diagram of a side view/cross section of theuniversal equipment date sensor 300 showing a system 400 for assemblingthe sensor 300 and attaching the sensor 300 to the equipment inaccordance with one embodiment of the invention. In this embodiment, asensor holder 480 is mounted to the equipment surface 495 via tape 430or another adhesive. Separately, the electronics are installed in thecomponent area 312 of the PCB 310 and a battery holder 450 withelectrical contacts for communicating battery power to the circuit isinstalled on PCB 310 opposite the electronics 312. A battery 440 is theninstalled in the battery holder 450. The PCB 310 with the battery andthe electronics is then placed in the sensor holder 480 and a plasticcover 470 with sealing material 460 around its perimeter is placed overtop of the PCB to protect the sensor 300 from moisture, dirt, and otherdebris. Screws 490 are then passed through holes in the plastic cover470 and holes 305 in the PCB 310 and screwed into threaded holes in thesensor holder 480 in order to secure the sensor 300 and the cover 470 tothe sensor holder 480 and, thereby, to the equipment surface 495.

FIG. 5 provides an exploded view of another system 500, somewhatdifferent from the one shown in FIG. 3B, for attaching the universalequipment data sensor 300 (or another equipment data sensor 230) to apiece of equipment in accordance with an embodiment of the invention. Inthis embodiment, a plastic base 508 is secured to an equipment surfacevia screws (not shown) through holes 514. The plastic base 508 includesa cylindrical housing in which a first flexible sealing ring 506 isplaced, followed by the sensor 300 (hear having a circular PCB), anothersealing ring 504, and finally a plastic cover 502. The sealing rings 506and 504 function to resist moisture and debris from reaching the sensor300, but also create a snug fitting for holding the perimeter of the PCBwhile allowing free space for the electrical components. In theillustrated embodiment, the plastic cover 502 is secured to the plasticbase 508 by inserting slides 512 into catches 510 and turning the cover502 ninety degrees relative to the base 508 to tighten the cover 502 tothe base 508.

Data Collection Process

FIG. 6A illustrates a process 600 by which the fleet management system100 captures information about a fleet of outdoor power equipment andoperators and uses the captured information to provide useful data andservices to users 203 of the system, according to some embodiments ofthe invention. As block 605 illustrates, the equipment data sensor 230in each piece of equipment 202 periodically captures and stores dataabout the equipment 202 and/or the equipment's environment from one ormore sensors 249/222 on the equipment (which may or may not be locatedon the equipment data sensor 230 itself). In some embodiments, theequipment data sensor 230 is built into the equipment 202 when theequipment 202 is manufactured. In other embodiments, the equipment datasensor 230 is installed by the fleet owner, a dealer, or a serviceperson after purchase of the equipment 202.

In some embodiments, the sensors 249 of the equipment data sensor 230capture data about the equipment 202 and/or the equipment's environment,and then the processing device 232 stores the data 244 in the memory240. In some embodiments, sensors 222 located on the equipment 202, butnot on the equipment data sensor 230, capture data about the equipment202 and/or the equipment's environment, and then the processing device232 communicates with the equipment's control system 212 to capture thisdata 244 and store it in the memory 240. The data captured about theequipment and/or its environment may be, for example, GPS or otherlocation data, engine speed (e.g., motor shaft RPM), component speed(e.g., PTO speed, cutting blade RPM, etc.), acceleration, orientation,ambient temperature, engine temperature, component temperature, nearbyequipment ID codes, nearby communication system ID codes, throttlestatus, PTO status, brake status, clutch status, user input commands,switch status, fuel level status, oil level status, battery levelstatus, operator presence in a seat or other operator station, heading,run time, ignition status, vibration, shock, tire level, tire condition,differential locking, wheel spinning, wheel slipping, chain tension,belt tension, humidity, moisture, pressure, altitude, tampering,equipment hatch opening or closing, component replacement, and/or otherparameters/metrics about the equipment's status, use, operation, and/orenvironment. As such, the sensors 249/222 may include such sensors asGPS receivers, RPM antennas, three-axis accelerometers or otheraccelerometers, electro-mechanical switches, thermocouples or othertemperature sensors, proximity sensors, fluid level sensors, pressuresensors, moisture sensors, motion detectors, magnets and magnetic fieldsensors, RF antennas, infrared sensors, transducers, lasers, and/orother sensors.

In some embodiments, the processing device 232 uses the clock 248 toperiodically (e.g., every minute) poll the sensors 249 or the equipmentcontrol system 212 to capture data 244 at that moment in time. Theprocessing system 232 then stores this data 244 in the memory 240 in theform of data packets that have timestamps and/or are arranged insequential order according to time.

As illustrated by block 610 in FIG. 6, the equipment data sensor 230also looks for signals from any nearby operator ID units 250. Forexample, in some embodiments, the processing device 252 of the operatorID units 250 uses the short-range transceiver 264 to periodically (e.g.,every few seconds) or continuously transmit a wireless signal having theID code 255 stored therein. Meanwhile, the processing device 232 of theequipment data sensor 230 periodically (e.g., every minute) uses itstransceiver 234 to look within a relatively short range for the presenceof any signals transmitted from any operator ID units 250.

If the processing device 232 identifies an operator's ID unit 250 withinthe range, then, as illustrated by block 615, the processing device 232reads the ID code 255 from the received signal and stores the ID code255 in the memory 240 with the captured sensor data as part of each datapacket for as long as the signal from the ID unit 250 is still beingreceived. If multiple ID units are found within a predetermined range,then those ID codes are also included in the data packets for as long asthey continue to be in range. In order to determine if the ID unit 250is still present, the processing device 232 may use the transceiver 234to periodically look for the ID unit's signal at substantially the sametime that the processing device 232 periodically captures data 244 fromthe sensors 249/222.

As illustrated by decision diamond 620, it is also periodicallydetermined whether the electronic data sensor 230 is within range of adata communication system 260. For example, in some embodiments, theprocessing device 262 of the data communication system 260 continuouslytransmits a wireless signal using its medium/long range transceiver 264.The processing device 232 of the equipment data sensor 230 mayperiodically (e.g., every several seconds or minutes) look for a signalfrom a data communication system 260. As illustrated in FIG. 6, if theprocessing device 232 of the equipment data sensor 230 does not finditself within range of the data communication system's transceiver 264,then it continues its routine of periodically capturing data and IDcodes and checking for any data communication systems 260 (blocks605-620).

As illustrated by block 625, if the processing device 232 of theequipment data sensor 230 does receive a signal from the datacommunication system's transceiver 264, then the processing device 232may use the equipment data sensor's transceiver 234 to communicate thedata 244 stored in the memory 240 to the data communication system 260.As also illustrated, in some embodiments the processing device 232 mayalso continue its process of collecting data while it is alsotransmitting data to the data communication system 260. In otherembodiments, the processing device 232 may halt the data collectingprocedures while the data 244 is being uploaded to the datacommunication system 260.

In some embodiments, the processing device 232 may also require that oneor more other conditions be satisfied before it begins uploading thedata 244 to the data communication system 260. For example, in someembodiments, the processing device 232 may wait until the equipment'sengine is turned off or the equipment is stationary before it transmitsthe data 244 to the data communication system 260. In some embodiments,the data communication system 260 is powered up automatically when theequipment 202 is powered down. For example, if the equipment 202 ispowered down within range of a data communication system 260, theequipment data sensor 230 may send a signal to a the data communicationsystem 260 waking it up so that the equipment data sensor 260 can uploadthe data 244 to it.

As illustrated by block 630, the data communication system 260 thencommunicates the data 244 to the data management server system 270.Specifically, the processing device 262 uses the network interface 265to make a connection to the data management sensor system 270 over thenetwork 206 and transmit the data 244 (and in some embodiments ID codes255 and 269 as described above) to the data management server system 270using the appropriate communication protocol(s) based on the network 206used.

As illustrated by block 635, the data management server system 270stores and processes the data 244 received from the one or more datacommunication systems 260. As described in greater detail elsewhereherein with regard to the other Figures, the processing device 274 ofthe data management server system 270 executes a fleet management serverapplication 278 to calculate other parameters from the data and/or usethe data and calculated parameters to create charts, graphics, tables,alerts, tools, communications, outputs, etc. that assist a user 203 withmanagement of a fleet of outdoor power equipment (or other equipment)and/or equipment operators. Much of the output and services provided tothe user 203 by the fleet management system 100 is provided via a fleetmanagement portal hosted on the network 206 by the data managementserver system 270. For example, the fleet management portal may includea web portal version and a mobile app portal version. In addition to thefleet management portal, the data management server system 270 may sendinformation or commands back to the equipment data sensor 230 so thatthe equipment data sensor 230 can take some action, control some part ofthe equipment 202 (e.g., control fuel supply and/or ignition timing ofan internal combustion engine), and/or present information to theoperator 204. Further, some embodiments of the data management serversystem 270 send text messages, emails, or other communications outsidethe fleet management portal directly to client computing devices 290

As such, as illustrated by block 640, the data management server system270 communicates processed data to one or more network-enabled clientcomputing devices 290 (which may be mobile devices or other personalcomputing devices), equipment data sensors 230 or control systems 212,and/or other output or feedback to systems interested in the data. Insome embodiments this communication is in the form of a fleet managementweb portal, embodiments of which may be described in more detail hereinbelow. With regard to the fleet management portal, different users 203may have different access rights which provide different levels ofinformation access, tools, and/or portals.

As mentioned above, the data collection and data communication steps ofprocess 600 may be, in some embodiments, performed continuously,simultaneously, and/or at regular intervals, while in other embodimentssome steps may be performed only in response to certain conditions whichmay prompt different modes of operation during which some of the stepsof process 600 are performed while others are not. For example, FIG. 6Bis a flow chart illustrating various modes of operation of an embodimentof the equipment data sensor 230 and a process 680 that may be performedby the equipment data sensor 230 for selecting the proper mode ofoperation and communicating with other devices in the fleet managementsystem, according to some embodiments of the invention. The process 680illustrated in FIG. 6B may be particularly advantageous in situationswhere the equipment data sensor 230 is self-powered by its own battery(e.g., as embodiments of the universal equipment data sensor 300 may be)since the process 680 may prolong battery life relative to otherprocesses for collecting and communicating data.

Referring now to blocks 681 and 682 in the flow chart of FIG. 6B, when abattery is inserted into the equipment data sensor, the equipment datasensor first enters into a “shelf mode” 682. In the shelf mode 682, theequipment data sensor uses very little, if any, power (e.g.,approximately 4.14 μA) and, as such, does not transmit any dataexternally nor communicate with any ID units or data communicationsystems.

As represented by decision diamond 683, if the equipment data sensor isin shelf mode 682 and it detects that the engine is turned on (e.g., viareceipt of a signal from the RPM sensor or some other sensor thatdetects engine operation), then the equipment data sensor will enter an“engine-on mode” 684. In some embodiments the equipment data sensor willwait until the engine is running for at least some small predefinedperiod of time (e.g., ten seconds) before it enters the engine-on state684. When in the engine-on mode 684, the equipment data sensor willperiodically sample and process data from the one or more sensors it isin communication with, such as RPM data from the engine RPM sensor. Theequipment data sensor will also use its transceiver to periodicallysearch for any nearby operator ID units. The equipment data sensor willgenerally consume more power operating in the engine-on mode 684 than inany of the other modes. In the illustrated embodiment, the equipmentdata sensor does not attempt to find or communicate with any datacommunication systems (e.g., base stations) while in the engine-on mode684. In the illustrated embodiment where the equipment data sensorutilizes a vibration sensor to sense vibration of the equipment datasensor, the equipment data sensor also disables this vibration sensor inthis state to conserve power. In general, whenever the engine is turnedon (at least for some small predefined minimum amount of time), then theequipment data sensor enters the engine-on mode 684, regardless of whichmode it is in at the time.

As represented by decision diamonds 685 and 686, if the equipment datasensor determines that the engine has been turned off and determinesthat it has in its memory data that it collected about the equipment,the operator, or the equipment's operation that has not yet beencommunicated to a data communication system, then the equipment datasensor enters into an “active base station search mode” 687. However, ifthe equipment data sensor determines that the engine has been turned offand determines that it does not have any data that needs to becommunicated to a data communication system, then the equipment datasensor enters into a “passive base station search mode” 692.

In the active base station search mode 687, the equipment data sensoruses its transceiver to actively search for data communication systems(e.g., base stations) within range by periodically (e.g., every tenseconds) transmitting base station search packages. The base stationsearch package tries, for example, up to three times in every attempt ifno acknowledgement is received from the data communication system. Assuch, in one embodiment, the equipment data sensor sends up to eighteenpackets each minute making the active base station search relativelypower consuming, too.

As illustrated by decision diamonds 688 and block 690, if a datacommunication system (e.g., a base station) acknowledges a transmissionfrom the equipment data sensor, then the equipment data sensor transmitsdata packages stored in its memory to the data communication system inattempts to transfer all of the data that has not yet been transferredto a data communication system, using for example, the transceiver and aproprietary communication protocol. As represented by decision diamond691, if the equipment data sensor receives permission from the datacommunication system indicating that the data communication system hassuccessfully received all of the data that the equipment data sensorneeds to transmit, then the equipment data sensor enters the passivebase station search mode 692.

As illustrated by decision diamonds 688 and block 689, in someembodiments, if the equipment data sensor does not receiveacknowledgement from a data communication sensor and does not sensevibration using its vibration sensor for some predefined period of time(e.g., five minutes), then the equipment data sensor enters the passivebase station search mode.

As mentioned above, the equipment data sensor will also go out of theactive base station search mode 687 and into the engine-on mode 684 whenthe engine is turned on and allowed to run for some predefined minimumamount of time.

The passive base station search mode 692 is designed to reduce powerconsumption and, in one embodiment, the main difference between thepassive base station search mode 692 and the active base station searchmode 687 is the longer time between transmissions of search packages.For example, in some embodiments, the equipment data sensor in thepassive base station search mode 692 will only transmit packages onceevery 300 seconds.

As illustrated by decision diamonds 693, 694, and 695, the equipmentdata sensor will remain in the passive base station mode until itdetermines (using its sensors and/or clock) that any one of threedifferent events happen. Specifically, as represented by decisiondiamond 693, if the equipment data sensor senses some predefined minimumamount of vibration (e.g., some minimum vibration amplitude and/orlength of time of vibration sensed by the vibration sensor) then, ifthere is data stored in the equipment data sensor that still needs to betransmitted to a data communication system, then the equipment datasensor again enters the active base station search mode 687. Asrepresented by decision diamond 694, the equipment data sensor will alsogo out of the passive base station search mode 692 and into theengine-on mode 684 when the engine is turned on and allowed to run. Asrepresented by decision diamond 695, if the equipment data sensor is inthe passive base station search mode 692 and detects that it has notbeen used for 30 days (or some other predefined and relatively lengthyperiod of time), then it enters back into the previously-describedextremely-low-power shelf mode 682. Otherwise it continues in thepassive base station search mode 692 until one of the three conditions693, 694, and 695 is satisfied.

Operator-Equipment Pairing

In situations where the equipment data sensor 230 detects two or moreoperator ID codes 255 within range, the fleet management system 100 mayautomatically determine which operator is operating the equipment 202 onwhich the equipment data sensor 230 is located. FIGS. 7A and 7Billustrate a process by which the fleet management system 100 locatesmultiple persons within proximity to a piece of equipment and determineswhich one of these people is the operator of the piece of equipment.Specifically, FIGS. 7A, 7B and 7C provide a schematic diagram and flowcharts illustrating operator-equipment pairing according to someembodiments of the invention.

FIG. 7A shows a piece of equipment 705 (here a string trimmer) includingan equipment data sensor 720 thereon. The equipment 705 is operated by aperson named Karl 710, who holds an operator ID unit 730. Two otherpersons, Linda 712 and Sven 714, work nearby and also have their ownoperator ID units 732 and 734, respectively.

Referring to block 752 in the process flow 750 shown in FIG. 7B, theequipment data sensor 720 of the equipment 705 periodically captures andstores data about the equipment 705 from one or more sensors on theequipment, as described in greater detail above. As illustrated by block754, concurrently with capturing data from the sensors, the equipmentdata sensor 720 also periodically looks for ID units within apredetermined range. As described above and as illustrated in thegraphic 745 in FIG. 7A, the equipment data sensor 720 is arranged to becapable of receiving, and preferably also of transmitting, short rangeradio frequency signals. The operator ID units 730, 732, and 734 arecarried by three operators 710, 712, and 714 shown in FIG. 7A and arearranged to transmit radio frequency communication signals, such as, butnot limited to, frequencies that are typically unlicensed.

In some embodiments, the equipment data sensor's transceiver has amaximum range that can be varied between five centimeters and thirtymeters by varying the power available depending on the situation. Forinstance, in the case of communication between the equipment data sensor720 and an operator ID unit 730 it may suffice with only a narrow range(e.g., maximum two meters) while the communication between an equipmentdata sensor 720 and a base station (not shown) might require a rangemore vast (e.g., twenty meters or more). A low-power short-range signalmay be desired when searching for ID units so that the equipment datasensor 230 does not identify too many ID units at one time and so that,as described below, signal strength between multiple identified ID unitsare distinguishable, thereby allowing for an approximation of relativedistance to each identified ID unit.

The equipment data sensor 720 is designed to receive any signaltransmitted from an operator ID unit and store the related specificoperator ID code obtained therefrom in the memory of the equipment datasensor 720. As illustrated in graphic 745 in FIG. 7A, intercommunicationcould, for instance, be performed in time intervals in order to saveenergy. For example, the equipment data sensor 720 could be activated tolisten to known ID units once every minute, while said ID units could beactivated to transmit their ID-codes once every second. Furthermore, theequipment data sensor 720 may be configured to only look for newoperator ID units every several minutes. An example of this type ofprocess for identifying and monitoring nearby ID units is illustrated inFIG. 7C and described in greater detail below.

In FIG. 7A, Karl 710 is operating the equipment 705 and is thereforewell within the range of the equipment data sensor 720. As such, theequipment data sensor 720 quickly finds Karl's ID unit 730 and listensapproximately every minute for the ID code communicated by Karl's IDunit 730. This listening by the equipment data sensor 720 issynchronized with its capturing of equipment data from the sensors, andthe equipment data sensor 720 stores Karl's ID code with the sensor datain a new data packet periodically (approximately every minute in theillustrated example). Because Karl 710 and his ID unit 730 are veryclose to the equipment data sensor 720, the equipment data sensor 720receives a strong radio signal and many data packages with little, ifany, interruption (brief interruptions due to random interferences maybe possible as Karl 710 is operating the equipment 705).

When the equipment data sensor 720 searches again for nearby ID units,not only does it still find Karl's ID unit 730, it also finds Linda's IDunit 732 because Linda 712 has begun working within the broadcastingrange of the equipment data sensor 720. Accordingly, the equipment datasensor 720 stores both Linda's ID code and Karl's ID code in each datanew data packet that it stores in its memory along with thecorresponding sensor data, until it stops receiving signals from one orboth of the two ID units. Without more, one could not know by looking atthe data packages whether Linda 712 was merely in close proximity to theequipment 705 operated by Karl 710 or whether Linda actually took overoperation of the equipment 705 and Karl 710 merely remained in thevicinity. However, since embodiments of the invention track operatorperformance, it can be very important to the accuracy and/or usefulnessof the information that the fleet management system 100 can accuratelyidentify the actual equipment operator and the roles of other nearbypersons.

In order to assist with determining which ID code represents the actualoperator of the equipment 705, the equipment data sensor 720 is, in someembodiments, configured to identify and record a received signalstrength indicator (RSSI) which is a measure of the signal strength ofthe ID code signal received from a ID unit (e.g., the power present inthe received radio signal as measured by the power generated in theantenna of the equipment data sensor's transceiver). As illustrated byblock 756 in FIG. 7B, the RSSI value of each transmission that theequipment data sensor 720 listens to is recorded in each data packetcreated by the equipment data sensor 720 along with the corresponding IDcode. In one embodiment, the RSSI ranges between −100 dB and −1 dB.

As illustrated by graphic 740 in FIG. 7A, RSSI (and signal strengthgenerally) is a function of distance and decreases as the distancebetween the ID unit and the equipment data sensor 720 increases. In someembodiments, certain zones are created to approximate different areas ofdistance (e.g., zone A=very close proximity to equipment; zone B=closeproximity to equipment; and zone C=medium to long distance fromequipment) and the fleet management system 100 recognizes these zones bya RSSI value that marks the transition from one zone to another.

In some embodiments, the equipment data sensor 720 is configured toignore (e.g., not store or identify) ID units having a RSSI below acertain threshold in order to reduce noise or data that is not likely tobe useful. For example, in the embodiment illustrated in FIG. 7A, theequipment data sensor 720 may be configured to ignore, filter-out, orotherwise exclude Sven 714 from the ID codes stored in the current datapacket since the RSSI (here 0.7) of the radio signal currently receivedfrom Sven's ID unit 734 does not surpass a particular threshold (e.g.,within zone C).

As illustrated by block 758 in FIG. 7B, the equipment data sensor 720transmits data to the data management server system (e.g., via a basestation or other data communication system). As illustrated by block760, the data management server system then automatically determineswhich ID code corresponds to the operator of the equipment 705 based atleast in part on RSSI (i.e., signal strength), number of data packages,and/or other information received about operation of the equipment 705and nearby equipment. For example, the highest RSSI generally indicatesthe operator, however, the data management server system may also lookat the number of data packages received and the change in the RSSI overtime since the operator ID code will typically be seen in most datapackets received and, while it may not be the highest RSSI at all pointsin time, it will usually be the highest RSSI for most points in time.Other data that may also be used in the data management server system'salgorithm may include, for example, information about whether theequipment 705 is running and/or ID codes and RSSI values received fromother nearby equipment that indicate that one of the ID codes is clearlyassociated with the operator of the other equipment and therefore cannotlikely be the operator of equipment 705. In the illustrated embodiment,Karl's RSSI is 4.0, is fairly regular, and his ID code is present inmany data packages, while Linda's RSSI is 1.3 and is also fairlyregular, but her ID code is included in somewhat fewer data packages.Therefore, the data management server system 270 would determine thatKarl is the most likely operator and would identify in the database thatKarl was the operator at this point in time. Once this is determined, itmay also be used, in some embodiments, by the data management serversystem 270 to help determine that Karl is not likely to be operatingother equipment at the same time, despite other equipment sensing Karl'sID unit amongst one or more other operator ID units. An example of aprocess performed by the data management server system 270 to use RSSIvalues and other information to determine the likely operator isdescribed in greater detail below.

As illustrated by block 762, the data management server system may alsobe configured to determine and flag (e.g., send out an alert in thefleet management portal) any safety concerns or other issues based onRSSI of non-operators and the operational status of the equipment 705.For example, the data management server system may be configured toalert the fleet owner or a team manager, in near real-time or after thefact, if Linda's RSSI value indicated that she crossed into zone A whileequipment 705 had its cutting element in operation.

Although the flow charts describe an embodiment of the fleet managementsystem where the operator is determined at the server level of the fleetmanagement system, other embodiments may be configured so that theequipment data sensor, or even the data communication system, performsthis operation of determining which ID code from a plurality of sensedID codes represents the equipment operator at each point in time.

In some embodiments of the invention, the equipment data sensor 230 isarranged to also transmit radio signals so that two or more poweredmachines within broadcasting range of each other are able to sense eachother's presence using their equipment data sensors 230. As a safetymeasure the fleet management system may comprise a warning systemarranged to alert a user of a powered machine in case the equipment datasensor registers a radio signal transmitted from another machine withinits broadcasting range or with greater than some signal strengththreshold. Such an alert may be any or a combination of audio, visual,or tactile signals such as for instance a sound alarm, a light signaland/or vibration signals. Hereby, unintentional interference between twooperators may be prevented or avoided. In some embodiments instead of orin addition to a warning system, the fleet management system creates asafety record that is presented to a user after the fact.

In cases where the equipment is powered by a combustion engine, saidcommunication device may further include a safety system arranged to beactivated in case the equipment data sensor registers a signaltransmitted from another machine within a pre-set range, where thesafety system when activated may be arranged to put the engine of thepowered machine on idle, shut off the engine, disengage the clutch,shutoff the PTO, and/or the like. This can be achieved for instance bymeans of restricting the fuel supply and/or air supply as has beendescribed for instance in U.S. Patent Application Publication No.2011/0095215. Also this aspect may prove to be advantageous in order tominimize the risk of two operators interfering with each other's work.

FIG. 7C is a flow chart illustrating a process 770 that may be performedby an equipment data sensor 720/230 (e.g., via the processing deviceexecuting computer-readable program code stored in the memory andutilizing the transceiver, sensors, clock, and/or memory devicesaccording to rules specified by the code) to look for, monitor, andstore operator identification codes from a plurality of operatoridentification units within range of the equipment data sensor,according to some embodiments of the invention. This process may beperformed as part of steps 754 and 756 of the process illustrated inFIG. 7B.

As represented by block 772 in FIG. 7C, when the equipment data sensor720 determines that the engine is running (e.g., it senses engine RPMusing the engine RPM sensor) it then, as represented by block 774,spends some particular period of time (e.g., one minute) looking for anyID units within range.

As represented by decision diamond 776 and block 778, if the equipmentdata sensor 720 does not identify any ID units within range, then itwaits some particular period of time (e.g., seven minutes) beforereturning to step 774 to try again to find any nearby ID units.

As represented by decision diamond 776 and block 780, when the equipmentdata sensor 720 does identify one or more ID units, then the equipmentdata sensor determines the number of ID units that can be identified andeach ID unit's specific transmission period (since each ID unit will beperiodically transmitting signals many times per minute and the periodsof ID unit's transmission cycle will likely be offset in time at leastslightly).

As represented by block 782, based on the number of ID units and theirspecific transmission periods, the equipment data sensor 720 calculatesa schedule for exactly when to listen to each ID unit once per minute(of course, periods of time other than one minute are also possible inother embodiments).

As represented by blocks 784 and 786, the equipment data sensor thenspends a particular period of time (e.g., fourteen minutes) listeningfor each identified ID unit's transmission according to the calculatedsynchronization schedule and storing the ID codes and RSSI values foreach ID unit's transmission. After the period of time expires, theequipment data sensor may then then return to step 774 to again look forany and all of the ID units within range and repeat the above-describedprocess for another, for example, fifteen minute session.

The illustration 745 in FIG. 7A shows conceptually an example of how theoperator sensing technique described with reference to FIG. 7C works. Itshould be appreciated that there are basically two modes in thisillustration: an operator search mode and an operator synchronizationmode. The first mode, the operator search mode, starts in minute 0 andfinishes in minute 1. This mode is later repeated between minute 8 andminute 9 of the RPM session. During the first operator search session,the equipment data sensor 720 managed to find operator ID unit 710.After the first operator search session ends, the equipment data sensor720 will enter the first operator synchronization session where it willattempt to synchronize with the ID unit 710 once per minute. Theequipment data sensor 720 will record if there was a “hit” or if therewas not for each minute. In this example, the equipment data sensor 720managed to have three hits in the first eight minutes of the RPMsession. In minute 8, a second operator search session was started andlasted a minute. During this second operator search session, twooperator ID units were found: ID unit 710 (again) and ID unit 712. Atthe conclusion of the second operator search session, the secondoperator synchronization session begins and the same procedure describedfor the first synchronization session repeats but with the equipmentdata sensor 720 synchronizing with both ID units according to a schedulewhere it is specifically looking for each identified ID unit once perminute, but with slightly offset cycles so that it synchronizes witheach ID unit at different points in time during each minute. In theexample shown in FIG. 7A, the equipment data sensor 720 received 3“hits” with the ID unit 710 and 3 hits with the ID unit 712 during thesecond operator synchronization schedule. After the whole RPM sessionends (e.g., when the engine is turned off) the data from the equipmentdata sensor 720 will be put in a table and analyzed by the datamanagement server system 270 to determine which of the ID codes 710 and712 represented the operator of the equipment associated with theequipment data sensor 720 during the sessions when both ID codes wherereceived.

Process for Deciding Who is the Operator:

When there is more than one detected operator in the module data, thedata management server system 270 uses logic in the operator module ofthe parser module 278B to decide which of the ID codes is the oneassociated with the operator who is actually the one operating themachine. To do this, in one embodiment the data management server system270 goes through one or more tests until it reaches a particular levelof confidence that one of the ID codes represents the operator.

Test 1—Unique Operator

The first test that the server 270 performs is to check if in theoperator table if there is one or no operators. If there are nooperators, then the result of the pairing will be unknown and theprocess stops for this session. If the operators list has only oneoperator, then that operator will be paired with the equipment as theoperator and, in some embodiments, no more tests will be performed. Ifthere are two or more operators, then the server 270 proceeds to thenext test to check some other variables in the operators table toattempt to pair the equipment with a single operator.

In one embodiment, for every Operator Session there could be up to fiveOperator Search Sessions, so the following calculations may need to beperformed for every Operator Search Session. For every Operator SearchSession there will be one or several “wining operator” and the operatoror operators that appear in more “winning” session lists will be the onethat should be paired to the equipment data sensor 230 and, thereby, tothe equipment 202.

Test 2—Synchronized Hits

The first variable to consider will be the Synchronized Hits; thisvariable represents how many times the equipment data sensor 230 foundthe operator between two search sessions. It is not possible just to seewhich operator has the greatest amounts of hits, because then the server270 would eliminate all other important information like RSSI. So theoperator with the greatest amount of hits has at least a certainpercentage more hits than the operator with the second greatest amountof hits. This percentage difference is called the Synchronized HitsThreshold. This threshold is a value between 0 and 1.

The server 270 first organizes the operators in an array arranged indescending order by synchronized hits where the operator with thegreatest amount of hits is in position 0 (Operator[0]) and the operatorwith the least amount of hits is in the last position (Operator[TDO-1]).

After the arrangement by synchronized hits is done, the server 270checks if the operator at position 0 has more hits than the operator atposition 1 and has at least the Synchronized Hits Threshold differencebetween both of them. For example, in one embodiment, this threshold hasa value of 0.2. As such, the test may be codes something like this:

if (Operator[0].SynchronizedHits > (Operator[0].SynchronizedHits * (1 +SynchronizedHitsTH))) { /*The Operator has been found*/ returnOperator[0]; }

If this test fails, then the server 270 next will eliminate all theoperators that have less synchronized hits than the operator with thehighest amount of synchronized hits multiplied by 1 minus theSynchronized Hits Threshold. So any operator that has less synchronizedhits than: (Operator[0].SynchronizedHits*(1−SynchronizedHitTH)), will beeliminated. This means that in the next test the server will have feweroperators to work with.

Test 3—Average Synchronized Hits RSSI

The next variable to check is the Average Synchronized Hits RSSI. Asimilar logic must be applied to the new check in that the server willalso have an Average Synchronized Hits RSSI Threshold which will have avalue between 0 and 1. For example, this threshold may be set to have avalue of 0.1. The next thing for the server 270 to do is to organize theremaining operators in descending order in terms of the AverageSynchronized Hits RSSI. Once this is done, the server 270 checks if theoperator at position 0 has a greater Average Synchronized Hits RSSI thanthe operator at position 1 and at least having the Average SynchronizedHits Threshold difference between both of them. The check may be codedsomething like this:

if (Operator[0].AverageSynchronizedRSSI >(Operator[0].AverageSynchronizedRSSI * (1 + AverageSynchronizedRSSITH))){ /*The Operator has been found*/ return Operator[0]; }

If this check doesn't yield any result, then the server 270 will try toeliminate some operators in a way very similar to the previouselimination. Specifically, all the operators are eliminated that haveless Average Synchronized Hits RSSI than the operator with the highestAverage Synchronized Hits RSSI multiplied by 1 minus the AverageSynchronized Hits Threshold. This means that all operators with lessAverage Synchronized RSSI than: (Operator[0].AverageSynchronizedRSSI*(1−SynchronizedHitTH)), will be eliminated fromthe list.

Test 4—Average Search RSSI

The next variable that the server 270 considers is the Average SearchRSSI by applying the same logic as before:

(i) organize the operators in descending order in terms of AverageSearch RSSI;

(ii) check if the difference of Average Search RSSI between the operatorat position 0 and the operator at position 1 is at least the AverageSearch RSSI of operator 0 multiplied by 1 minus the Average Search RSSIThreshold (suggested value 0.1);

(iii) if there is no result from the check, then eliminate all operatorsthat have a smaller RSSI than the operator at position 0 multiplied by 1minus the Average Search RSSI Threshold (Operator[0].AverageSynchronizedRSSI*(1−AverageSearchRSSITH)).

Test 5—Search packages

The next, and in this embodiment the final, variable that the server 270considers and is the Search packages, again following a similar routine:

(i) organize the operators in descending order in terms of Searchpackages;

(ii) check if the difference of Search packages between operator atposition 0 and the operator at position 1 is at least the Searchpackages of operator 0 times the Search Packages Threshold (suggestedvalue 0.3); and

(iii) if there is no result from the check, eliminate all operators thathave a smaller RSSI than the operator at position 0 times the SearchPackages Threshold (Operator[0]. SearchPackages*(1−SearchPackagesTH)).

If after analyzing all the operator variables there is still not asingle “winner,” then the server 270 should select all operators aswinners, and then check the next Search session. After selecting thewining operator(s) of the first Search Session, the server 270 does thesame evaluation for all other Search Sessions. After evaluating allSearch Sessions there will be one or several winning operator(s) perSearch Session. So the operator that appears the most in the winner listacross all Search Sessions is the one that should be paired with theequipment data sensor 230 and, thereby, to the equipment 202. If thereare two or more operators with the same amount of Search Sessions won,then the server may then make one final test.

Test 6—Random or Historic Selection

In the final test the server may select all the operators that have thesame number of wins. Then out of this list the server 270 may select oneof them randomly, or use other history parameters to be able to decidewhich operator should be paired. For example, if in the last tensessions Operator Number 1000 was paired to this equipment data sensor230, and suddenly we have a session with a very tight decision betweenOperator Number 1000 and Operator Number 2012, then because of historyparameters the server should select Operator 1000 again. In anotherexample, if Operator Number 2012 is already paired with anotherequipment data sensor during this period of time and that equipment datasensor is associated with equipment that is not likely to be used at thesame time as equipment 202, then Operator 2012 may be eliminated.

The skilled person realizes that a large variety of modifications may beperformed and are contemplated and made known or obvious by the abovedescription. For instance, according to one aspect of the invention amachine which has been operated is arranged to be paired with theoperator who has been running/handling the machine in order to later beable to evaluate e.g. performance for training purposes. This can beachieved in different ways. According to some embodiments of theinvention, one way is to provide the machine with a communication deviceable to receive and store an ID-code associated with an operator. TheID-code can be transmitted to the communication device as an RF-signal,via WiFi or any other suitable communication signal. The communicationdevice will subsequently send all registered information, includingstored values of parameters associated with running of the machine andID-code/s, to a server, and the pairing is thereafter done at aserver-level. However, another possibility is that the operator activelyidentifies himself/herself to the communication device, for instance bymeans of submitting a code (e.g. a code number) by means of a keypadconnected to the communication device or by means of biometrics, meaningthe pairing is done already at the machine level and the communicationdevice will register the proper user by means of registering said codenumber.

Yet another possibility is that the identification unit is a cell phonecontaining the ID-code in a data-packet which can be transmitted to thecommunication device, where the pairing between the operator and themachine is done either already in the cell phone or in the communicationdevice which receives the ID-code from the cell phone. Common for manyof the embodiments is the collection and storing of data associated withrunning of the machine, pairing of the machine with the operator andevaluating the information. Evaluation is preferably done in a server.The server may be a remote, stationary server e.g. in a control centre,or it may be a mobile smart phone which can be used in close connectionto the working fleet.

In various example embodiments described herein, a device (e.g., anequipment data sensor 230, a data communication system 260, a datamanagement server system 270, a client computing device 290, etc.),which may comprise one or more sub-devices, may execute certainfunctionalities described above by employing software. When software isemployed, it should be understood that the software may functionresponsive to the operation of processing circuitry configured toexecute the corresponding functionalities. In some embodiments, theprocessing circuitry may include at least a memory and a processor. Thememory may include one or more non-transitory memory devices such as,for example, volatile and/or non-volatile memory that may be eitherfixed or removable. The memory may be configured to store information,data, applications, instructions or the like for enabling thecorresponding device to carry out various functions in accordance withexemplary embodiments of the present invention. For example, the memorycould be configured to buffer input data for processing by theprocessor. Additionally or alternatively, the memory could be configuredto store instructions for execution by the processor. As yet anotheralternative, the memory may include one or more databases that may storea variety of data sets responsive to input from a sensor network orother devices described herein. Among the contents of the memory,applications may be stored for execution by the processor in order tocarry out the functionality associated with each respective application.

The processor may be embodied in a number of different ways. Forexample, the processor may be embodied as various processing means suchas one or more of a microprocessor or other processing element, acoprocessor, a controller or various other computing or processingdevices including integrated circuits such as, for example, an ASIC(application specific integrated circuit), an FPGA (field programmablegate array), or the like. In an example embodiment, the processor may beconfigured to execute instructions stored in the memory or otherwiseaccessible to the processor. As such, whether configured by hardware orby a combination of hardware and software, the processor may representan entity (e.g., physically embodied in circuitry—in the form ofprocessing circuitry) capable of performing operations according toembodiments of the present invention while configured accordingly. Thus,for example, when the processor is embodied as an ASIC, FPGA or thelike, the processor may be specifically configured hardware forconducting the operations described herein. Alternatively, as anotherexample, when the processor is embodied as an executor of softwareinstructions, the instructions may specifically configure the processorto perform the operations described herein. As such, in someembodiments, the processor (or the processing circuitry) may be said tocause each of the operations or functions described in connection withthe devices mentioned above by directing, responsive to the execution ofcorresponding instructions and/or algorithms, the storage, processing,generation, display, rendering, and/or communication of the data and/orinformation as described herein.

As will be appreciated by one of skill in the art, the present inventionmay be embodied as a method (including, for example, acomputer-implemented process, a business process, and/or any otherprocess), apparatus (including, for example, a system, machine, device,computer program product, and/or the like), or a combination of theforegoing. Accordingly, embodiments of the present invention may takethe form of an entirely hardware embodiment, an entirely softwareembodiment (including firmware, resident software, micro-code, etc.), oran embodiment combining software and hardware aspects. Furthermore,embodiments of the present invention may take the form of a computerprogram product on a computer-readable medium having computer-executableprogram code embodied in the medium.

Any suitable transitory or non-transitory computer readable medium maybe utilized. The computer readable medium may be, for example but notlimited to, an electronic, magnetic, optical, electromagnetic, infrared,or semiconductor system, apparatus, or device. More specific examples ofthe computer readable medium include, but are not limited to, thefollowing: an electrical connection having one or more wires; a tangiblestorage medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), or other optical or magnetic storage device.

In the context of this document, a computer readable medium may be anymedium that can contain, store, communicate, or transport the programfor use by or in connection with the instruction execution system,apparatus, or device. The computer usable program code may betransmitted using any appropriate medium, including but not limited tothe Internet, wireline, optical fiber cable, radio frequency (RF)signals, or other mediums.

Computer-executable program code for carrying out operations ofembodiments of the present invention may be written in an objectoriented, scripted or unscripted programming language such as Java,Perl, Smalltalk, C++, or the like. However, the computer program codefor carrying out operations of embodiments of the present invention mayalso be written in conventional procedural programming languages, suchas the “C” programming language or similar programming languages.

Embodiments of the present invention are described above with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products. It will be understood thateach block of the flowchart illustrations and/or block diagrams, and/orcombinations of blocks in the flowchart illustrations and/or blockdiagrams, may be implemented by computer-executable program codeportions. These computer-executable program code portions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce aparticular machine, such that the code portions, which execute via theprocessor of the computer or other programmable data processingapparatus, create mechanisms for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer-executable program code portions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the code portions stored in the computer readablememory produce an article of manufacture including instructionmechanisms which implement the function/act specified in the flowchartand/or block diagram block(s).

The computer-executable program code may also be loaded onto a computeror other programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that the codeportions which execute on the computer or other programmable apparatusprovide steps for implementing the functions/acts specified in theflowchart and/or block diagram block(s). Alternatively, computer programimplemented steps or acts may be combined with operator or humanimplemented steps or acts in order to carry out an embodiment of theinvention.

As the phrase is used herein, a processor/processing device may be“configured to” perform a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing particular computer-executable programcode embodied in computer-readable medium, and/or by having one or moreapplication-specific circuits perform the function. As used herein, theterms “determine” or “determining” do not necessarily mean determiningan exact value and, instead, are meant to include “estimate” and“estimating” unless explicitly stated otherwise.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of, and not restrictive on, the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations, combinations, andmodifications of the just described embodiments can be configuredwithout departing from the scope and spirit of the invention. Therefore,it is to be understood that, within the scope of the appended claims,the invention may be practiced other than as specifically describedherein.

The invention claimed is:
 1. A fleet management system for assistingwith management of one or more pieces of equipment and one or moreequipment operators, the fleet management system comprising: anidentification unit configured to be worn or carried by one of the oneor more equipment operators, wherein the identification unit comprisesan identification unit transmitter communicably coupled to anidentification unit memory, wherein the identification unit memorycomprises stored therein an operator identification code uniquelyassociated with a specific operator, and wherein the identification unitis configured to wirelessly communicate the operator identification codevia the identification unit transmitter; and an equipment data sensorassociated with a specific piece of equipment, the specific piece ofequipment being one of the one or more pieces of equipment, theequipment data sensor comprising a processing device communicablycoupled to a sensor memory, a receiver, and at least one sensorconfigured to sense data about operation of the specific piece ofequipment or the specific piece of equipment's environment, wherein theat least one sensor comprises an engine revolution per minute (RPM)sensor, wherein the processing device of the equipment data sensor isconfigured to: use the receiver to receive the operator identificationcode transmitted by the identification unit transmitter; store theoperator identification code in the sensor memory with the data aboutoperation of the specific piece of equipment or the specific piece ofequipment's environment, wherein the data about the operation of thespecific piece of equipment or specific piece of equipment's environmentcomprises sensed RPM of an engine of the specific piece of equipmentbetween start and shutdown of the engine; and sense a measure ofstrength of signals received from the identification unit transmitterand a second identification unit transmitter associated with a secondidentification unit, the second identification unit transmitter beingassociated with a second operator identification code; wherein themeasure of the strength of signal received from the identification unittransmitter and the measure of the strength of signal received from thesecond identification unit transmitter are used to determine which ofthe operator identification code or the second operator identificationcode is associated with an actual operator operating the specific pieceof equipment.
 2. The fleet management system of claim 1, wherein theprocessing device of the equipment data sensor is communicably coupledto a transceiver comprising the receiver and a transmitter, and whereinthe processing device is further configured to: use the transceiver tocommunicate the operator identification code and the data aboutoperation of the specific piece of equipment or the specific piece ofequipment's environment to a remote data management server.
 3. The fleetmanagement system of claim 2 further comprising the data managementserver, wherein the data management server is configured to utilize theoperator identification code and the data about operation of thespecific piece of equipment or the specific piece of equipment'senvironment to provide a user of a fleet management portal withinformation about the specific operator associated with theidentification code and the operator's use of the specific piece ofequipment associated with the equipment data sensor.
 4. The fleetmanagement system of claim 3, further comprising: a plurality ofidentification units each comprising a different operator identificationcode stored therein, each operator identification code uniquelyassociated with a different operator of the one or more equipmentoperators; a plurality of equipment data sensors each associated with adifferent piece of equipment of the one or more pieces of equipment,wherein the data management server is configured to receive data fromeach of the plurality of equipment data sensors, the data from each ofthe plurality of equipment data sensors comprising one or more operatoridentification codes and data about operation of the specific piece ofequipment or the specific piece of equipment's environment, and whereinthe data management server provides the user of the fleet managementportal with information about the plurality of operators and operationof the one or more pieces of equipment.
 5. The fleet management systemof claim 2, wherein the equipment data sensor's processing device isconfigured to use the transceiver to communicate the operatoridentification code and the data about the specific piece of equipment,operation of the specific piece of equipment, or the specific piece ofequipment's environment to the remote data management server via atleast one data communication system.
 6. The fleet management system ofclaim 5, further comprising: a data communication system comprising awireless transceiver communicably coupled to a network interface coupledto a global communication network, wherein the data communication systemuses the wireless transceiver to receive the operator identificationcode and the data about operation of the specific piece of equipment orthe specific piece of equipment's environment from the equipment datasensor, and wherein the data communication system uses the networkinterface to communicate the operator identification code and the dataabout operation of the specific piece of equipment or the specific pieceof equipment's environment to the remote data management server via theglobal communication network.
 7. The fleet management system of claim 5,wherein the data communication system comprises a base station orsatellite station located in a storage facility for storing the specificpiece of equipment or in a vehicle for transporting the specific pieceof equipment.
 8. The fleet management system of claim 1, wherein theequipment data sensor comprises a power source, the sensor memory, thereceiver, and the at least one sensor.
 9. The fleet management system ofclaim 1, wherein the equipment data sensor can be installed on aplurality of different types of equipment without modification of theequipment data sensor's components.
 10. The fleet management system ofclaim 1, wherein the equipment data sensor comprises a self-powereddevice that wirelessly senses the data about the specific piece ofequipment, operation of the specific piece of equipment, or the specificpiece of equipment's environment so that the equipment data sensor canbe installed on a plurality of different types of equipment, at thefactory or after-market, by adhering the self-powered device to thespecific piece of equipment without further modification of the specificpiece of equipment.
 11. The fleet management system of claim 1, whereinthe at least one sensor further comprises a temperature sensor, andwherein the data about the operation of the specific piece of equipmentor the specific piece of equipment's environment further comprisestemperature data associated with the specific piece of equipment or thespecific piece of equipment's environment.
 12. The fleet managementsystem of claim 1, wherein the engine RPM sensor comprises an antennaconfigured to sense engine RPM by sensing electromagnetic wavesgenerated in an ignition cable in the specific piece of equipment. 13.The fleet management system of claim 1, further comprising: a magnetattached to an engine flywheel, wherein the engine RPM sensor isconfigured to sense the magnet on the engine flywheel to sense engineRPM, and wherein the equipment data sensor is powered at least in partby electromagnetic induction caused by the magnet on the engineflywheel.
 14. The fleet management system of claim 1, wherein the one ormore pieces of equipment comprise one or more pieces of outdoor powerequipment, and wherein the specific piece of equipment comprises atrimmer, a chainsaw, a blower, or a lawn mower.
 15. The fleet managementsystem of claim 1, wherein the one or more pieces of equipment compriseone or more pieces of both wheeled and handheld outdoor power equipment.16. The fleet management system of claim 1, wherein the at least onesensor further comprises one of: a global positioning system (GPS)receiver, a three-axis accelerometer, an accelerometer, anelectro-mechanical switch, an inclinometer, a thermocouple or othertemperature sensor, a proximity sensor, a fluid level sensor, a pressuretransducer, a moisture sensor, a motion detector, a magnetic fieldsensor, an radio frequency (RF) antenna, an infrared sensor, a laser, ashock sensor, a speed sensor, or a vibration sensor.
 17. The fleetmanagement system of claim 1, wherein the at least one sensor is furtherconfigured to sense data about operation of the specific piece ofequipment, and wherein the data about the operation of the specificpiece of equipment comprises one of: location data, engine speed,component RPM, power take-off (PTO) system speed, acceleration,orientation, incline, ambient temperature, engine temperature,transmission temperature, component temperature, nearby equipmentidentification (ID) code, nearby communication system ID code, throttlestatus, PTO engagement status, brake status, clutch status, user input,switch status, fuel consumption, fuel level status, oil level status,battery level status, voltage, electrical current, velocity, operatorpresence, heading, run time, ignition status, vibration, shock, tirelevel, tire condition, differential locking, wheel spinning, wheelslipping, humidity, force, signal strength, moisture, tension, pressure,altitude, tampering, equipment hatch opening, or component replacement.18. The fleet management system of claim 1, wherein the processingdevice of the equipment data sensor is configured to use the receiver toreceive the second operator identification code transmitted by thesecond identification unit transmitter, and wherein the processingdevice of the equipment data sensor is further configure to distinguishbetween the operator identification code and the second operatoridentification code based at least partially on strength of signalsreceived from the identification unit transmitter and the secondidentification unit transmitter.
 19. A fleet management system forassisting with management of one or more pieces of equipment and one ormore equipment operators, the fleet management system comprising: anidentification unit configured to be worn or carried by one of the oneor more equipment operators, wherein the identification unit comprisesan identification unit transmitter communicably coupled to anidentification unit memory, wherein the identification unit's memorycomprises stored therein an operator identification code uniquelyassociated with a specific operator, and wherein the identification unitis configured to wirelessly communicate the operator identification codevia the identification unit transmitter; and an equipment data sensorassociated with a specific piece of equipment, the specific piece ofequipment being one of the one or more pieces of equipment, theequipment data sensor comprising a processing device communicablycoupled to a sensor memory, a receiver, and at least one sensorconfigured to sense data about the specific piece of equipment,operation of the specific piece of equipment, or the specific piece ofequipment's environment, wherein the processing device of the equipmentdata sensor is configured to: use the receiver to receive the operatoridentification code transmitted by the identification unit transmitter;and store the operator identification code in the sensor memory with thedata about the specific piece of equipment, operation of the specificpiece of equipment, or the specific piece of equipment's environment;and a data management server, wherein the processing device of theequipment data sensor is configured to use the receiver to receive asecond operator identification code transmitted by a secondidentification unit transmitter associated with a second identificationunit, wherein the processing device of the equipment data sensor isfurther configured to sense a measure of strength of signals receivedfrom the identification unit transmitter and the second identificationunit transmitter, and wherein a processing device of the data managementserver is configured to receive the measure of strength of the signalsand determine, based at least partially on the measure of strength ofthe signals, which of the operator identification code or the secondoperator identification code is associated with an actual operatoroperating the specific piece of equipment at the time that the measureof signal strength was measured, wherein the processing device of thedata management server is further configured to: associate the dataabout the specific piece of equipment, operation of the specific pieceof equipment, or the specific piece of equipment's environment with theoperator identification code or the second operator identification codethat it determines to be the actual operator operating the specificpiece of equipment at a time proximate to when the data was measured,and use the data to provide output about the actual operator'sperformance or work conditions, and wherein the identification unitcomprises a passive radio frequency tag that is powered at least in partby electromagnetic waves received from the equipment data sensor andcommunicates with the equipment data sensor in response to receiving theelectromagnetic waves from the equipment data sensor.
 20. A method ofmonitoring equipment and/or equipment operators, the method comprising:providing at least one of a plurality of operators with anidentification unit to be worn or carried by the operator whenever theoperator is operating the equipment, wherein the identification unitcomprises an identification unit transmitter communicably coupled to anidentification unit memory, wherein the identification unit memorycomprises stored therein an operator identification code that can beuniquely associated with one of the plurality of operators, and whereinthe identification unit is configured to wirelessly communicate theoperator identification code via the identification unit transmitter;providing at least one of a plurality of pieces of equipment with anequipment data sensor associated with a specific piece of equipment, theequipment data sensor comprising a processing device communicablycoupled to a sensor memory, a receiver, and at least one sensorconfigured to sense data about operation of the specific piece ofequipment or the specific piece of equipment's environment, wherein theat least one sensor comprises an engine revolution per minute (RPM)sensor; automatically receiving, by the equipment data sensor via thereceiver, the operator identification code transmitted by theidentification unit transmitter; storing, by the equipment data sensor,the operator identification code in the sensor memory with the dataabout operation of the specific piece of equipment or the specific pieceof equipment's environment, wherein the data about the operation of thespecific piece of equipment or specific piece of equipment's environmentcomprises sensed RPM of an engine of the specific piece of equipmentbetween start and shutdown of the engine; sensing, by the equipment datasensor, a measure of strength of signals received from theidentification unit transmitter and a second identification unittransmitter associated with a second identification unit, the secondidentification unit transmitter being associated with a second operatoridentification code; and determining, by the equipment data sensor,based on the measure of the strength of signal received from theidentification unit transmitter and the measure of the strength ofsignal received from the second identification unit transmitter, whichof the operator identification code or a second operator identificationcode is associated with an actual operator operating the specific pieceof equipment.